BrowserslistError: Unknown version 0 of and_chr
See original GitHub issueSteps to reproduce
- browserslist@1.5.2 postcss@5.2.11 webpack@2.2.0
- browserslist config in the package.json
...
"browserslist": [
"> 1% in RU",
"last 2 versions"
]
...
- postcss.config.js is simple
module.exports = {
plugins: [
require('postcss-import')(),
require('autoprefixer')()
]
};
NODE_ENV=production webpack --hide-modules --bail
throws
ERROR in ./styles/index.css
Module build failed: ModuleBuildError: Module build failed: BrowserslistError: Unknown version 0 of and_chr
at error (~/{path_to_project}/node_modules/browserslist/index.js:29:11)
at Function.select (~/{path_to_project}/node_modules/browserslist/index.js:555:21)
at ~/{path_to_project}/node_modules/browserslist/index.js:180:41
at Array.forEach (native)
at browserslist (~/{path_to_project}/node_modules/browserslist/index.js:169:13)
at isSupported (~/{path_to_project}/node_modules/caniuse-api/dist/index.js:75:10)
at ~/{path_to_project}/node_modules/postcss-merge-rules/dist/lib/ensureCompatibility.js:87:66
...
PS
- NODE_ENV != production -> ok
- not use “> 1% in RU” -> ok
- use “> 1% in US” -> not ok
Issue Analytics
- State:
- Created 7 years ago
- Comments:17 (9 by maintainers)
Top Results From Across the Web
BrowserslistError: Unknown version 55 of and_chr · Issue #128
Right now a temporary fix is setting the version key to 0 instead of 55 , otherwise this error is thrown: BrowserslistError: Unknown...
Read more >Webpack production build: BrowserslistError: Unknown ...
Sounds like you've got an outdated css-loader . Delete your node_modules and reinstall. That should fix it.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Technically it was Can I Use mistake. But it is hard to fix it there. So I add hack to Browserslist.
@ben-eb maybe we will fix it in you project. Can I use had version 0 in countries statistics, but 55 in global data.
Scratch that – it was just a fluke. It started consistently failing again with the same error. While twice as slow, switching from
npm install
toyarn
seems to be consistently working. Thanks!