Replies: 1 comment
-
This would fall outside what Next.js would handle internally, as the CSS module support is not built by Next and instead is just integrated into the Next framework. I think you'd want to request this feature from the css-loader project. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Feature request
A build-in CSS (SASS) Module behavior should be the same with Styled JSX
Is your feature request related to a problem? Please describe.
Naming a class should be the same as a default behavior (in the quote) instead of referring every class name to an object key.
Let's say we have a module css and a module js file as below, this is the current setup:
Describe the solution you'd like
A clear and concise description of what you want to happen:
When I worked with styled jsx, this is the current behavior:
So I'm expecting the import css-module should be the same, shouldn't it?
Describe alternatives you've considered
An alternative approach is:
Thanks,
Beta Was this translation helpful? Give feedback.
All reactions