Unknown browser query `dead`
See original GitHub issueWhen building with the latest version we came across this issue with the --prod --aot flags:
ERROR in ./node_modules/bootstrap/scss/bootstrap.scss[39m[22m[0m
[0m[1m[31mModule build failed: ModuleBuildError: Module build failed: BrowserslistError: Unknown browser query `dead`[39m[22m[0m
[0m[1m[31m at /home/default/workspace/Galleries/Sybrin.UI.Modules.AppBuilder/node_modules/browserslist/index.js:164:11[39m[22m[0m
[0m[1m[31m at Array.reduce (<anonymous>)[39m[22m[0m
[0m[1m[31m at resolve (/home/default/workspace/Galleries/Sybrin.UI.Modules.AppBuilder/node_modules/browserslist/index.js:132:18)[39m[22m[0m
[0m[1m[31m at browserslist (/home/default/workspace/Galleries/Sybrin.UI.Modules.AppBuilder/node_modules/browserslist/index.js:224:16)[39m[22m[0m
[0m[1m[31m at Browsers.parse (/home/default/workspace/Galleries/Sybrin.UI.Modules.AppBuilder/node_modules/autoprefixer/lib/browsers.js:61:16)[39m[22m[0m
[0m[1m[31m at new Browsers (/home/default/workspace/Galleries/Sybrin.UI.Modules.AppBuilder/node_modules/autoprefixer/lib/browsers.js:52:30)[39m[22m[0m
[0m[1m[31m at loadPrefixes (/home/default/workspace/Galleries/Sybrin.UI.Modules.AppBuilder/node_modules/autoprefixer/lib/autoprefixer.js:70:24)[39m[22m[0m
[0m[1m[31m at plugin (/home/default/workspace/Galleries/Sybrin.UI.Modules.AppBuilder/node_modules/autoprefixer/lib/autoprefixer.js:81:24)[39m[22m[0m
[0m[1m[31m at LazyResult.run (/home/default/workspace/Galleries/Sybrin.UI.Modules.AppBuilder/node_modules/postcss/lib/lazy-result.js:277:20)[39m[22m[0m
[0m[1m[31m at LazyResult.asyncTick (/home/default/workspace/Galleries/Sybrin.UI.Modules.AppBuilder/node_modules/postcss/lib/lazy-result.js:192:32)[39m[22m[0m
[0m[1m[31m at /home/default/workspace/Galleries/Sybrin.UI.Modules.AppBuilder/node_modules/postcss/lib/lazy-result.js:197:27[39m[22m[0m
[0m[1m[31m at <anonymous>[39m[22m[0m
[0m[1m[31m at runLoaders (/home/default/workspace/Galleries/Sybrin.UI.Modules.AppBuilder/node_modules/webpack/lib/NormalModule.js:195:19)[39m[22m[0m
[0m[1m[31m at /home/default/workspace/Galleries/Sybrin.UI.Modules.AppBuilder/node_modules/loader-runner/lib/LoaderRunner.js:364:11[39m[22m[0m
[0m[1m[31m at /home/default/workspace/Galleries/Sybrin.UI.Modules.AppBuilder/node_modules/loader-runner/lib/LoaderRunner.js:230:18[39m[22m[0m
[0m[1m[31m at context.callback (/home/default/workspace/Galleries/Sybrin.UI.Modules.AppBuilder/node_modules/loader-runner/lib/LoaderRunner.js:111:13)[39m[22m[0m
[0m[1m[31m at Promise.resolve.then.then.catch (/home/default/workspace/Galleries/Sybrin.UI.Modules.AppBuilder/node_modules/postcss-loader/lib/index.js:194:71)[39m[22m[0m
[0m[1m[31m at <anonymous>[39m[22m[0m
Build step 'Execute shell' marked build as failure
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:41 (13 by maintainers)
Top Results From Across the Web
Unknown browser query `dead` in React/Express App - Stack ...
I just got this when I tried to do a production build of my app. Looks like it is an issue with the...
Read more >Module build failed: BrowserslistError: Unknown browser ...
It happpens because of old cssnano (it uses old Browserslist without dead query). We are triting to release cssnano 4 (with new Browserslist) ......
Read more >Unknown browser query `dead`” #React #npm | Mixster
Sovling the browserlist error in ReactJS, angular, nodejs, npm and Vue through a simple quick fix.
Read more >Browserslist on Twitter: "If you have “BrowserslistError ...
If you have “BrowserslistError: Unknown browser query `dead`”,. @vipulgupta2048. wrote a good article about how to fix this issue.
Read more >Unknown browser query `dead` in React/Express App-Reactjs
It happens if you have another tool, which uses very old Browserslist. Call npm ls , find who use Browserslist < 4 and...
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 Free
Top 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

Thank you very much @XhmikosR @ai for being open to discussion & tackling this issue altogether. In our project we wanted to keep everything updated and a fix seemed like the way to go here. You guys backing up on each other is nice to know when someone encounters this kind of issue, so, thanks again for the good work 🎉
@mgol I will remove looking into
node_modulesin next major release. If there will be more packages with this config in npm package I will think to change in patch release