-
-
Notifications
You must be signed in to change notification settings - Fork 162
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
Version 5.2.6 hashes are different on Windows (Ok on Mac) #279
Comments
Sounds like an issue somewhere with converting paths. As I don't use Windows, I won't be able to help. PRs welcome. |
I have the same problem,Is there any way to solve this problem? |
In a project with Next.js and Scss, I suffered the same problem. Hope the following method can help you. Solution:
Reason:The documentation requires that In Mac system, slash in file path is Therefore, css-loader generates different hash values in mac and windows. Converting slashes is more reasonable. So I think it's a bug of css-loader.
|
Its seems that
|
it still not work for me T.T |
Dear auth:
bundle.css
.index__my-node___4029n{
Applied class name
class=".index__my-node___503l9"
package.json
"dependencies": {
"antd": "^3.19.5",
"babel-plugin-react-css-modules": "^5.2.6",
"dva": "^2.6.0-beta.6",
"lodash": "^4.17.15",
"moment": "^2.24.0",
"react": "^16.8.6",
"react-dom": "^16.8.6",
"styled-components": "^4.3.2",
"umi-request": "^1.2.6"
},
"devDependencies": {
"babel-eslint": "^9.0.0",
"eslint": "^5.4.0",
"eslint-config-umi": "^1.4.0",
"eslint-plugin-flowtype": "^2.50.0",
"eslint-plugin-import": "^2.14.0",
"eslint-plugin-jsx-a11y": "^5.1.1",
"eslint-plugin-react": "^7.11.1",
"husky": "^0.14.3",
"lint-staged": "^7.2.2",
"postcss-less": "^3.1.4",
"react-test-renderer": "^16.7.0",
"umi": "^2.7.7",
"umi-plugin-react": "^1.8.4"
},
babelPlugin config:
["react-css-modules", {
"filetypes": {
".less": {"syntax": "postcss-less"}
},
"generateScopedName": '[name]__[local]___[hash:base64:5]'
}]
css-loader version:
└─┬ [email protected]
└─┬ [email protected]
└─┬ [email protected]
└── [email protected]
generic-names version:
└─┬ [email protected]
├── [email protected]
└─┬ [email protected]
└── [email protected]
what else do you need ? please contact me.
thank you.
The text was updated successfully, but these errors were encountered: