Skip to content

Browserlist error when updating to v16 #24837

Closed

Description

@edbzn

Command

serve

Is this a regression?

  • Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

15

Description

When updating Angular to next (16.0.0-next.3) using ng update and running ng serve, I get the following error:

./my-project/src/main.ts - Error: Module build failed (from ./node_modules/@angular-devkit/build-angular/src/babel/webpack-loader.js):
BrowserslistError: [BABEL] /my-project/projects/todo-mvc/src/main.ts: Unknown version 110 of chrome (While processing: "base$0$0")

./my-project/src/polyfills.ts - Error: Module build failed (from ./node_modules/@angular-devkit/build-angular/src/babel/webpack-loader.js):
BrowserslistError: [BABEL] /my-project/projects/todo-mvc/src/polyfills.ts: Unknown version 110 of chrome (While processing: "base$0$0")

./node_modules/css-loader/dist/runtime/api.js - Error: Module build failed (from ./node_modules/@angular-devkit/build-angular/src/babel/webpack-loader.js):
BrowserslistError: [BABEL] /my-project/node_modules/css-loader/dist/runtime/api.js: Unknown version 110 of chrome (While processing: "base$0$0")

Minimal Reproduction

Repository where it happens.

Exception or Error

No response

Your Environment

Angular CLI: 16.0.0-next.3
Node: 16.18.1
Package Manager: yarn 1.22.5
OS: linux x64

Angular: 16.0.0-next.2
... common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1600.0-next.3
@angular-devkit/build-angular   16.0.0-next.3
@angular-devkit/core            16.0.0-next.3
@angular-devkit/schematics      16.0.0-next.3
@angular/cli                    16.0.0-next.3
@schematics/angular             16.0.0-next.3
rxjs                            7.4.0
typescript                      4.9.5

Anything else relevant?

No response

Activity

  1. JeanMeche commented on Mar 10, 2023

    @JeanMeche
    Member

    There is something wrong with your deps. Deleting the yarn.lock and reinstalling your deps fixes the issue.

  2. edbzn commented on Mar 10, 2023

    @edbzn
    Author

    Nice, it fixes the issue, thank you @JeanMeche. Any idea why it happened?

  3. edbzn commented on Mar 10, 2023

    @edbzn
    Author

    It seems to be a Babel version mismatch or something like this.

  4. JeanMeche commented on Mar 10, 2023

    @JeanMeche
    Member

    This error is thrown by Browserstist.

    I suspect an outdated deps to caniuse-lite. But unsure.

  5. angular-automatic-lock-bot commented on Apr 10, 2023

    @angular-automatic-lock-bot

    This issue has been automatically locked due to inactivity.
    Please file a new issue if you are encountering a similar or related problem.

    Read more about our automatic conversation locking policy.

    This action has been performed automatically by a bot.

  6. locked and limited conversation to collaborators on Apr 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions