Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resolve deprecated npm critters package #28857

Open
1 task done
Tymo66 opened this issue Nov 14, 2024 · 0 comments
Open
1 task done

Resolve deprecated npm critters package #28857

Tymo66 opened this issue Nov 14, 2024 · 0 comments

Comments

@Tymo66
Copy link

Tymo66 commented Nov 14, 2024

Command

build

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

No response

Description

Install packages with npm install for latest version of Angular-devkit/build-angular (18.2.11) pulls in a deprecated critters package that emits an npm warn message.

Minimal Reproduction

  • ng new tour-of-heroes
  • manual delete node_modules and package-lock.json (just to recreate blank situation)
  • npm install:

npm warn deprecated [email protected]: Ownership of Critters has moved to the Nuxt team, who will be maintaining the project going forward. If you'd like to keep using Critters, please switch to the actively-maintained fork at https://github.com/danielroe/beasties

Exception or Error

no warn message on deprecated packages, just clean message

Your Environment

Angular CLI: 18.2.11
Node: 20.16.0
Package Manager: npm 10.8.2
OS: win32 x64

Angular: 18.2.11
... animations, cli, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1802.11
@angular-devkit/build-angular   18.2.11
@angular-devkit/core            18.2.11
@angular-devkit/schematics      18.2.11
@schematics/angular             18.2.11
rxjs                            7.8.1
typescript                      5.5.4
zone.js                         0.14.10

Anything else relevant?

it's not really a bug, I just want to keep a clean build output, free of warnings and errors

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant