You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is not a question, feature request, RFC, or anything other than a bug report directly related to Gatsby. Please post those things in GitHub Discussions: https://github.com/gatsbyjs/gatsby/discussions
Description
Starting with a default starter project, after adding sass & react-css-modules, generated class names' hash parts are not matching.
Compare generated class names in markup & css. In my case "index-module--test---j_NR" vs "index-module--test---2PAo".
Expected Result
The generated component class name should match the generated css class name, and the style should be applied.
Actual Result
The generated component class name does not match the generated css class name, so the style is NOT applied.
In my case "index-module--test---j_NR" vs "index-module--test---2PAo".
Hi!
You don't need to use the plugin as Gatsby handles CSS modules by default already (including SASS). If you still want to use the babel plugin you'll need to adapt the plugin and use the fork that is mentioned in the issue you linked.
Preliminary Checks
Description
Starting with a default starter project, after adding sass & react-css-modules, generated class names' hash parts are not matching.
Probably related to gajus/babel-plugin-react-css-modules#291
Reproduction Link
https://gitlab.com/Hitunen/gatsby-css-module-stylename-bug
Steps to Reproduce
Expected Result
The generated component class name should match the generated css class name, and the style should be applied.
Actual Result
The generated component class name does not match the generated css class name, so the style is NOT applied.
In my case "index-module--test---j_NR" vs "index-module--test---2PAo".
Environment
Config Flags
No response
The text was updated successfully, but these errors were encountered: