Replies: 4 comments 4 replies
-
Besides server components, it seems that vanilla-extract currently doesn't work in client components with the app directory enabled in dev mode.
|
Beta Was this translation helpful? Give feedback.
-
Too bad that the Turbopack doc ( see https://turbo.build/pack/docs/comparisons/turbopack-vs-webpack ) states that : "In its alpha state, Turbopack cannot currently be configured with plugins. In the future, we plan to make Turbopack just as extensible as Webpack - though likely with an altered API." |
Beta Was this translation helpful? Give feedback.
-
For anyone too inpatient to wait, I've had good success using the Remix approach: https://github.com/markdalgleish/remix-vanilla-extract-prototype Note the tradeoffs, but future migration should be rather painless. |
Beta Was this translation helpful? Give feedback.
-
I'd post a comment in another discussion like this one, because i would like to use VE in Next 13, so after some search i've summarize this to someone with know how (wish i could do it, but i barely know how to use the libraries i need, let alone create a solution for some) enough to pull a PR or something. |
Beta Was this translation helpful? Give feedback.
-
Next.js 13 was announced with some exciting new features! https://nextjs.org/blog/next-13
Namely for vanilla extract:
For 1 CSS loading works pretty differently with react server components and requires bundler integration. Has vanilla extract been tested with server components? (I might test this in a couple weeks.)
For 2 I assume that means vanilla extract will need a new turbopack plugin?
Beta Was this translation helpful? Give feedback.
All reactions