With Next.js introducing the new App Directory routing, it also introduced support for Server and Client components. Styled-components don't gel well with server components due to their heavy reliance on the JS runtime. Tailwind, on the other hand, slides right in and performs beautifully!
We also love Tailwind and we believe it enhances the development process, making it faster with a superior developer experience.
$ npx styled2tailwind --help
Our mechanism runs in four distinct steps:
flowchart LR
RSI(Raw Styled Input) --> JSAST(JavaScript AST)
JSAST --> RCSS(Raw CSS)
RCSS --> TW(Tailwind CSS)
Command | Description |
---|---|
styled2tailwind --help |
Displays help command. |
styled2tailwind "src/*.jsx" |
Parses all .jsx files inside src directory (supports regex). |
styled2tailwind "src/*.jsx" --no-replace |
Instead of replacing styled components with tailwind, it appends the tailwind output at the end of the file. |
styled2tailwind "src/*.jsx" --no-conflicts |
Forcefully replaces styled components with tailwind in the markup without using git conflicts. |
This project is still in early beta, we already tracked some limitations and we will ship fix for those in very near future!
Contributions are always welcome! To contribute, please follow these steps:
If you're looking for help or simply want to share your thoughts about the project, we encourage you to join our Discord community. Here's the link: https://blazity.com/discord. It's a space where we exchange ideas and help one another. Everyone's input is appreciated, and we look forward to welcoming you.
This project is licensed under the MIT License. For more information, see the LICENSE file.