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

Print information about deprecated subdependencies #4227

Closed
zkochan opened this issue Jan 13, 2022 Discussed in #4217 · 0 comments · Fixed by #4231
Closed

Print information about deprecated subdependencies #4227

zkochan opened this issue Jan 13, 2022 Discussed in #4217 · 0 comments · Fixed by #4231
Milestone

Comments

@zkochan
Copy link
Member

zkochan commented Jan 13, 2022

Discussed in #4217

Originally posted by sindzicat January 11, 2022
Hello!

I use node.js 16 on Windows 10.

When I install gulp using pnpm I see the following:

λ pnpm add gulp
Packages: +294
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Packages are hard linked from the content-addressable store to the virtual store.
  Content-addressable store is at: P:\.pnpm-store\v3
  Virtual store is at:             node_modules/.pnpm
Progress: resolved 298, reused 295, downloaded 2, added 294, done

dependencies:
+ gulp 4.0.2
Already up-to-date
Progress: resolved 1, reused 1, downloaded 0, added 0, done

But when I use npm to install gulp I see additional info:

λ npm install gulp
npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
...

I see, that gulp.watch() won't work on Node.js 16 because gulp still uses chokidar 2.

I used pnpm to install gulp and didn't see such message. As result I was need a whole week to find why gulp.watch() don't work.

How to turn on such warnings in pnpm?

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

Successfully merging a pull request may close this issue.

1 participant