Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
[Docs] Recommend CSS Modules over css-in-js #15542
Open
Comments
lfades
changed the title
This was referenced Aug 15, 2020
|
As far as I know, webpack team wants to drop css-modules from css-loader but do you plan to implement css-modules on Next.js? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It has been mentioned multiple times on feedback that in the documentation for Built-In CSS Support we don't really recommend CSS Modules over CSS-in-JS, therefore we create confusion about what should be used if both methods handle the same thing.
We should update the page to be clear about the advantages of CSS Modules over css-in-js, mainly being that you don't need JS to add the CSS as CSS Modules are concatenated into many minified and code-split
.cssfiles. Ideally users should end up thinking that CSS Modules are the preferred solution, but any CSS-in-JS library is also an option.