bootstrap: Unknown browser query `dead`

When building with the latest version we came across this issue with the --prod --aot flags:

ERROR in ./node_modules/bootstrap/scss/bootstrap.scss
Module build failed: ModuleBuildError: Module build failed: BrowserslistError: Unknown browser query `dead`
    at /home/default/workspace/Galleries/Sybrin.UI.Modules.AppBuilder/node_modules/browserslist/index.js:164:11
    at Array.reduce (<anonymous>)
    at resolve (/home/default/workspace/Galleries/Sybrin.UI.Modules.AppBuilder/node_modules/browserslist/index.js:132:18)
    at browserslist (/home/default/workspace/Galleries/Sybrin.UI.Modules.AppBuilder/node_modules/browserslist/index.js:224:16)
    at Browsers.parse (/home/default/workspace/Galleries/Sybrin.UI.Modules.AppBuilder/node_modules/autoprefixer/lib/browsers.js:61:16)
    at new Browsers (/home/default/workspace/Galleries/Sybrin.UI.Modules.AppBuilder/node_modules/autoprefixer/lib/browsers.js:52:30)
    at loadPrefixes (/home/default/workspace/Galleries/Sybrin.UI.Modules.AppBuilder/node_modules/autoprefixer/lib/autoprefixer.js:70:24)
    at plugin (/home/default/workspace/Galleries/Sybrin.UI.Modules.AppBuilder/node_modules/autoprefixer/lib/autoprefixer.js:81:24)
    at LazyResult.run (/home/default/workspace/Galleries/Sybrin.UI.Modules.AppBuilder/node_modules/postcss/lib/lazy-result.js:277:20)
    at LazyResult.asyncTick (/home/default/workspace/Galleries/Sybrin.UI.Modules.AppBuilder/node_modules/postcss/lib/lazy-result.js:192:32)
    at /home/default/workspace/Galleries/Sybrin.UI.Modules.AppBuilder/node_modules/postcss/lib/lazy-result.js:197:27
    at <anonymous>
    at runLoaders (/home/default/workspace/Galleries/Sybrin.UI.Modules.AppBuilder/node_modules/webpack/lib/NormalModule.js:195:19)
    at /home/default/workspace/Galleries/Sybrin.UI.Modules.AppBuilder/node_modules/loader-runner/lib/LoaderRunner.js:364:11
    at /home/default/workspace/Galleries/Sybrin.UI.Modules.AppBuilder/node_modules/loader-runner/lib/LoaderRunner.js:230:18
    at context.callback (/home/default/workspace/Galleries/Sybrin.UI.Modules.AppBuilder/node_modules/loader-runner/lib/LoaderRunner.js:111:13)
    at Promise.resolve.then.then.catch (/home/default/workspace/Galleries/Sybrin.UI.Modules.AppBuilder/node_modules/postcss-loader/lib/index.js:194:71)
    at <anonymous>
Build step 'Execute shell' marked build as failure

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Reactions: 3
  • Comments: 41 (13 by maintainers)

Most upvoted comments

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_modules in next major release. If there will be more packages with this config in npm package I will think to change in patch release

Hey, calling other project decisions a ā€œmistakeā€ is not cool šŸ˜ it is software development, there are mistakes everywhere. In hardware (there are a lot of complain about x86), OS (only microkernel is good), VM (Node.js authors made a talk about his mistakes) and package manager.

In this world, just finding one person and blame him is not cool šŸ˜

I will add warning and will consider to change behavior if the problem will be repeated with some other project.

This error happened to many of us as well and locking Bootstrap to version 4.1.1 fixed the error (don’t know what the cause is yet). Check out https://github.com/browserslist/browserslist/issues/266

After performing what you suggested, I ran into the same error, but I don’t think it’s directly related to BS, in our case we’re using angular 5.2 with an angular CLI version of 1.7.4, which has a dependency on ā€˜autoprefixer’ (outdated) which itself has a dependency on an old version of browserslist, as you can tell by this comment https://github.com/browserslist/browserslist/issues/266#issuecomment-404676720. There’s something that bootstrap 4.1.2 doesn’t like about browserslist 2.*, don’t know what that would be. Thanks again for the quick reply @XhmikosR ! šŸ„‡