use-dark-mode VS next-mdx-remote

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?

next-mdx-remote

We are going to be using next-mdx-remote for this tutorial. Let us install it -

So, i was reading the docs and Next/MDX looks exactly what i need for my blog. Well, not exactly because having hundreds of Markdown Pages doesn't look the best way to store the pages, and i was wondering if are any way to generate those pages from a DataBase full of Markdown pages. I read about next-MDX-remote but i was wondering if is there a native way to do that.

next-mdx-remote, a community package maintained by Hashicorp that allows you to use MDX from outside your project.

Do note that Code Hike also works with Next MDX Remote and MDX Bundler however, we are going to look at a simple example with the official MDX plugin for Next.js.

Refer the next-mdx-remote github to learn more the use of plugins and how awesome things could be done using MDX.

You could try storing mdx in wordpress somehow (I'm not a wordpress expert) and using next-mdx-remote to render that at runtime. MDX can contain both markdown and react components.

MDX is an extension on Markdown which, lets you import custom React components into your blog posts. To use MDX with Next.js you need to use a separate package. There are a few choices with MDX-remote being a popular one, but it has some drawbacks. For that reason, I chose to use mdx-bundler.

Sandpack is a live coding environment that runs on the browser. It is made by the team behind CodeSandbox/. The main objective here is to provide interactive examples to play around with, to users. I see it being widely used in things like blog posts and documentation (in fact the, work in progress, new React Docs is using Sandpack). In this article, we are going to look at how to add Sandpack to a React Application and then we will look at integrating it with Next MDX Remote in a NextJS Application.