You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 6, 2021. It is now read-only.
As you can see, prose works fine with dark mode in the old system (except for the caveat about responsive classes addressed by that PR tailwindlabs/tailwindcss-typography#153 ):
However when I tried that in a derivative from that template using the new jit engine, prose doesn't work with dark mode.
What version of @tailwindcss/jit are you using?
v0.1.7
What version of Node.js are you using?
v14.15.1
What build tool (or framework if it abstracts the build tool) are you using?
Next.js (details below)
What browser are you using?
Chrome latest 64-bit 89.0.etc
What operating system are you using?
Windows 10
Reproduction repository
https://github.com/DoctorDerek/steven-terner.github.io/blob/master/pages/demo.js
Hi, I'm crossposting this from tailwindlabs/tailwindcss-typography#157 because it affects both libraries.
Following up on a comment from @danjac about tailwindlabs/tailwindcss-typography#153 -- there's a bug that I'm reporting to jit & typography.
Here's an example repo that uses dark theme with prose / Tailwind typography: https://github.com/timlrx/tailwind-nextjs-starter-blog/ (not jit) and it's live here: https://tailwind-nextjs-starter-blog.vercel.app/
As you can see, prose works fine with dark mode in the old system (except for the caveat about responsive classes addressed by that PR tailwindlabs/tailwindcss-typography#153 ):

However when I tried that in a derivative from that template using the new jit engine, prose doesn't work with dark mode.

Source code: https://github.com/DoctorDerek/steven-terner.github.io/blob/master/pages/demo.js Live version: http://steven-terner-github-io.vercel.app/demo (That page won't stay up for particularly long, but I didn't want to spin up a new project just for this issue, sorry.)
I'm happy to look into it more myself if you'd like to assign me to following up on it, but now I'm just the messenger 😀
The text was updated successfully, but these errors were encountered: