a streamlined CSS-in-JS solution tailor-made for Next.js, seamlessly combining the expressive power of styled-components syntax with efficient build-time extraction and minimal runtime footprint, ensuring optimal performance and easy integration with existing atomic CSS frameworks like Tailwind CSS
With #116 we ported basically all functionality from our babel plugin to the new swc plugin.
The playground was still only able to work with babel. After investigating the issue, it looks like swc doesn't work in the browser if we also need wasm plugins (related issue: https://github.com/swc-project/swc/discussions/3540).
So this PR moves the current documentation from vocs to fumadocs, which is itself a next.js application. This allows us to process the transformation on the server side with a simple next route handler.
With #116 we ported basically all functionality from our babel plugin to the new swc plugin.
The playground was still only able to work with babel. After investigating the issue, it looks like swc doesn't work in the browser if we also need wasm plugins (related issue: https://github.com/swc-project/swc/discussions/3540).
So this PR moves the current documentation from vocs to fumadocs, which is itself a next.js application. This allows us to process the transformation on the server side with a simple next route handler.