🐛 Upgrading to v16.1.0 gives me "Unknown version 114 of edge (While processing: "base$0$0")"

[bjornharvold]

Is this a bug report or a feature request?

• Bug Report
• Feature Request

Please provide the steps to reproduce the issue [Bug Report only]

• I upgraded from 16.0.5 to 16.1.0
• I made sure all Angular related libs were on 16.1.0
• I upgraded Typescript to 5.1.4

Please provide the expected behavior vs the actual behavior you encountered [Bug Report only]

No response

Please provide a screenshot if possible [Bug Report only]

No response

Please provide the exception or error you saw [Bug Report only]

When I start my app, I now receive:

./apps/travel-agent/src/main.ts - Error: Module build failed (from ./node_modules/@angular-devkit/build-angular/src/tools/babel/webpack-loader.js):
BrowserslistError: [BABEL] /Users/crash/git/monorepo-typescript/apps/travel-agent/src/main.ts: Unknown version 114 of edge (While processing: "base$0$0")

./node_modules/@angular-devkit/build-angular/node_modules/css-loader/dist/runtime/api.js - Error: Module build failed (from ./node_modules/@angular-devkit/build-angular/src/tools/babel/webpack-loader.js):
BrowserslistError: [BABEL] /Users/crash/git/monorepo-typescript/node_modules/@angular-devkit/build-angular/node_modules/css-loader/dist/runtime/api.js: Unknown version 114 of edge (While processing: "base$0$0")

### Is this a browser-specific issue? If so, please specify the device, browser, and version. [Bug Report only]

_No response_

### Description [Feature Request only]

_No response_

### Proposed solution [Feature Request only]

_No response_

### Alternatives considered [Feature Request only]

_No response_

[JeanMeche]

Hi, this is a classic issue with Browslerlist see #25165 & #24837

The quick fix is to delete the yarn.lock and reinstalling the dependencies.

[bjornharvold]

Right you are. Deleting node_modules and yarn.lock fixed the issue.

[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.}