rehype VS use-dark-mode

Add Remark and Rehype plugins

Astro content collection are as simple as a folder containing a bunch of Markdown (or Markdoc or MDX) files if that's the only thing you need, but they can also do relationship matching between different collections, frontmatter validation using zod and you can also customize how the markdown is parsed and translated to html using rehype and remark and their plugin ecosystem.

That's all to render the post as HTML, there are lots of things you can do to customize the results, you can check the remark plugins and rehype plugins to pass as props to and you can also take a look at some other bloggers if you're looking for different styles for example Lee Robinson's or if you liked mine.

Now we have our Cloudinary account set up, we can use it with Docusaurus. To do so, we need to create a rehype plugin. This is a plugin for the rehype HTML processor. It's a plugin that will transform the HTML image syntax into a Cloudinary URL.

The next idea was to use normal markdown images and to place the images in the public folder. This eliminates the need for static import and treats our image like a remote image. But in order to make this work, we have to tell next/image the dimensions of the image. If we would use a static import for the image, the import magic would provide the dimensions for us. To pass the width and height to the image component we use a rehype plugin called rehype-img-size.

Astro makes it easy to add Remark or Rehype plugins to your markdown. You can extend add a markdown property to the Astro config file, an add a function/plugin to the remarkPlugins property (the extendDefaultPlugins property is added to make sure the default plugins aren't overwritten by this config change):

rehype: "rehype is a tool that transforms HTML with plugins. These plugins can inspect and change the HTML. You can use rehype on the server, the client, CLIs, deno, etc."

This means that you can transform your HTML with tools like rehype or remark. You can find out more about the available options here.

The HTML syntax tree is transformed through rehype, and rendered to React components.

We will be using an npm package called use-dark-mode which is a custom hook used to implement the toggle functionality between light and dark mode.

you can implement this script https://github.com/donavon/use-dark-mode/blob/develop/noflash.js.txt

the useEffect hook expects a value for dark mode which in my case I just use use-dark-mode hook .

But we may want to allow users to choose between light and dark modes within the app UI and save the preferences. We can achieve this by injecting a simple script right after , reading the local storage, and setting the class name for light/dark mode on the HTML element. We could try to come up with something ourselves, or we can use this React hook that will do it for us.

For this hook, I am not going to show the code that makes the hook because it's a little more advanced, but you can check it out here. Nonetheless, I will still show you how to use it once it has been defined. This hook actually returns an object with the value and the functions required to toggle, enable, and disable dark mode, but it's still the same concept just written in a different way. You will need to write a little CSS to configure how your light mode and dark mode will look, but the toggling can be handled by the hook.

I'm facing a frustrating issue with implementing dark mode into my React application. My app reads from localStorage and applies the preferred theme (this is all done by use-dark-mode). Unfortunately, everytime the user opens the page, the default theme flashes before dark mode is enabled.

Binding to a React hook is like binding to any other function. Here's an example of a binding to use-dark-mode.

For activiating the .dark class, I'm using the excellent useDarkMode hook by Donavon West which you'll need to install:

I had started implementation using Theme Context when I discovered use-dark-mode. They had all my requirements in a single hook, so why re-invent the wheel?