-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: add module.parser.css.namedExports #7274
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
src/content/configuration/module.mdx
Outdated
}; | ||
``` | ||
|
||
When `namedExports` is `false` (default behavior) for CSS modules, you can retrieve CSS classes using various import methods. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For webpack default behavior
is named export, so let's rewrite it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One note, thank you for your PR
src/content/configuration/module.mdx
Outdated
```js | ||
import * as styles from './styles.css'; | ||
import styles1 from './styles.css'; | ||
import { foo } from './styles.css'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's use styles.modules.css
because it is recommended named convention
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
Fix #7222