The other day I was reminded of two neat tricks related to customizing your favicon to bring some delight to your website visitors and also to improve your development flow - all thanks to !
If you want to skip right to the code, checkout both recipes in my repo!
The first recipe is a neat way to change the favicon of your site based on the preferred color scheme of the visitor. You can use the <link /> tag's media attribute
to have the browser "choose" the preferred icon based on light or dark mode.
If you're writing plain old html (or using some framework that gives you control over the html), you can use the below snippet to accomplish this:
<head>
<link rel="icon" href="./light-mode-favicon.ico" media="(prefers-color-scheme: light)" />
<link rel="icon" href="./dark-mode-favicon.ico" media="(prefers-color-scheme: dark)" />
</head>If you're using Next.js and it's metadata or generateMetadata exports, you can do the following:
export const metadata: Metadata = {
title: "Custom light/dark mode favicons",
description: "Generated by create next app",
icons: [
{
rel: "icon",
url: "./sun-favicon.ico",
media: "(prefers-color-scheme: light)",
},
{
You can see this recipe in action on this Next app!
This is a pretty neat trick that makes it just a bit easier to determine if you're looking at the development version of your site or the production one.
We've all been there, we're about 45 minutes into trying to debug an issue, you keep making more basic and basic changes to the code, refreshing the page in the browser and still can't see your changes. Only to then realize that you've been madly refreshing the production site expecting to find your local changes.
With a custom icon for development, you'll no longer get stuck in that situation again!
If you're using Next.js and it's metadata or generateMetadata exports, you can do the following:
export const metadata: Metadata = {
title: "Custom favicon per environment",
description: "Generated by create next app",
icons: [
{
rel: "icon",
url: process.env.NODE_ENV === "production" ? "./env-favicon.ico" : "./env-favicon-dev.ico",
}
You can see this recipe in action on this other Next app!
Let me know if you know of other tips and tricks with customizing your site's favicon!
Loading...
....
I've once again updated my personal website, this time powered by my own RSC framework and a custom CMS solution as well!
....
Are we reinventing the wheel when it comes to onboarding new AI agents to a codebase, when we already have primitives available for onboarding humans?
....
....
....
A quick tip for creating roundup or summary notes based on other notes in Obsidian using the Dataview plugin!
....
Have you ever found the need to change the image you render on a web page based on the current preferred color scheme of your theme?
....
I recently launched a rewrite and redesign of this personal website, I figured I'd talk a bit about the changes and new features that I added along the way!
....
A quick tip outlining how to provide specific TypeScript type definitions for a local module!
....
Slicing software: why vertical is better than horizontal.
....
What if you could author an entire web application in a single file?
....
Is it a good or a bad thing to offload writing code to AI agents and Large Language Models?
....
A brief look at Import Maps and package.json#imports to support isomorphic JavaScript applications!
....
A collection of tech talks that I regularly re-watch and also recommend to everyone!
....
Some features and functionality that I'd like within a React Server Component compatible framework.
....
A (running) collection of Bluesky tips, tools, packages, and other misc things!
....
How to generate a custom Ghostty theme based on any iterm2 theme!
....
A rough mental model for how you should be leveraging AI as a tool for your own growth
....
Even more thoughts on dogfooding!
....
The secret to excellent product teams is using your own product, and often!
....
(Ab)using Git as yet another tool for thought!
....
A quick look at the applications and tools that I (generally) use day to day for web development!
....
There's a common gotcha when creating Web Request and Response instances with Headers!
....
Feature toggles are often underused by most software development teams, and yet offer so much value during not only feature development but also refactors
....
A quick introduction to my new side project, hohoro. An incremental JS/TS library build tool!
....
webpack, and tools built on it like Next.js, don't support true dynamic imports, but I found a way to trick the system!
....
I've been using a variety of AI tools as of late, I figured I'd document the ones I'm primarily using!
....
I've started to use Cloudflare to manage my domains for several side projects, have had to jump through the same hooks multiple times that I figured I should document them here!
....
Revising my previous blog post on React Error Boundaries and my preferred go-to implementation!
....
The various risks and pitfalls of open source software run by corporations.
....
A monorepo template for managing a library and documentation together.
....
How we solved an almost show-stopping production bug, and how you can avoid it in your own projects.
....
When did semver major changes become so scary?
....
No I don't mean those Milano cookies you keep taking from the office snack wall either (although you should probably stop snacking on those as often as well).
....
Pair programming can be good sometimes - but not all the time
....
A few quick thoughts on burn out and taking a break
....
I've once again updated my personal website, this time powered by my own RSC framework and a custom CMS solution as well!
....
Are we reinventing the wheel when it comes to onboarding new AI agents to a codebase, when we already have primitives available for onboarding humans?
....
Have you ever found the need to change the image you render on a web page based on the current preferred color scheme of your theme?
....
A quick tip for creating roundup or summary notes based on other notes in Obsidian using the Dataview plugin!