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
Maybe we could add an experimental flag in the withYak config to automatically transpile styled-components code to next-yak. This feature would allow users to easily test existing styled-components-based projects with next-yak, potentially identifying performance improvements and compatibility issues.
Benefits:
Easier migration path for existing styled-components projects
Quick performance comparison between styled-components and next-yak
Identify areas where next-yak might need additional features to fully support styled-components syntax
Proposed Implementation:
Add a new experimental flag in withYak config, e.g., library: "styled-components"
When enabled, the loader would detect and transform styled-components imports to the next-yak equivalent
At the moment we don't support 100% of all features that styled-components has. Is the idea to somehow bail out if we find something that we don't support or just generate a warning?
Maybe we could add an experimental flag in the
withYak
config to automatically transpilestyled-components
code tonext-yak
. This feature would allow users to easily test existing styled-components-based projects with next-yak, potentially identifying performance improvements and compatibility issues.Benefits:
Proposed Implementation:
withYak
config, e.g.,library: "styled-components"