-
-
Notifications
You must be signed in to change notification settings - Fork 188
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v0.2 #89
v0.2 #89
Conversation
This pull request is being automatically deployed with Vercel (learn more). next-themes-basic – ./examples/example🔍 Inspect: https://vercel.com/paco/next-themes-basic/BLa2jTB8WtgScdZ4Fv9PFKoHMBpC next-themes-tailwind – ./examples/tailwind🔍 Inspect: https://vercel.com/paco/next-themes-tailwind/Ct5v453mbkAZhaQKkpLY7ngx7A1f |
I was bothered by the first flash with latest version, and then I found this, now I'm using |
We're running into the following error that occurs in the beta build & on v0.1.1.
<script>
!function() {
var d = document.documentElement.classList;
d.remove('light', 'dark');
d.style.colorScheme = 'dark';
d.add('dark')
}()
</script> We're using Tailwinds in the same app and have the following props set: <ThemeProvider
attribute="class"
defaultTheme="dark"
forcedTheme="dark" |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
I was delaying this PR in hopes that vercel/next.js#36364 would fix the bug in Next.js where So, let's move ahead with a regular script tag at the top of the body. I was worried not putting the script inside |
next/script
(see discussion in "Do not add <script> tags using next/head" message in development mode #84). This should be safe, because I've always documented that you should putThemeProvider
in_app
– but there may some cases where people have nested ThemeProvider.Fixes #107
Fixes #106
Fixes #99
Fixes #94
Fixes #90