I am getting following npm WARN deprecated although these packages are not in package.json file. Where these packages are listed? and where should i change their versions?

npm WARN deprecated [email protected]: One of your dependencies needs to upgrade to fsevents v2: 1) Proper nodejs v10+ support 2) No more fetching binaries from AWS, smaller package size
npm WARN deprecated [email protected]: core-js@<3.0 is no longer maintained and not remended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.

I am getting following npm WARN deprecated although these packages are not in package.json file. Where these packages are listed? and where should i change their versions?

npm WARN deprecated [email protected]: One of your dependencies needs to upgrade to fsevents v2: 1) Proper nodejs v10+ support 2) No more fetching binaries from AWS, smaller package size
npm WARN deprecated [email protected]: core-js@<3.0 is no longer maintained and not remended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.

• javascript
• angular
• npm
• npm-install
• package.json

• If you want to hide this warn, you just need to install fsevents as a optional dependency. Just execute: npm i fsevents@latest -f --save-optional ..And the warn will no longer be a bother. – developerKumar Commented Nov 22, 2019 at 7:47
• Does this answer your question? How to deal with deprecation warnings from npm – Dan Dascalescu Commented May 29, 2020 at 19:36

2 Answers 2

If these packages are not in your package.json, then they must be in package-lock.json which maintains the dependencies of dependencies mentioned in your package.json .

You can simply update the packages which are giving warning. Or maybe you can suppress these warning messages, npm gives various options to do it. Have a look at this.

These packages are not listed because they are dependencies of other packages that you use, they are not in your json file but some of the packages that are using them need them.

I don't think you have any problems updating them, but I remend saving your status anyway. You can update your project on github up to this point, and if something happens with the update you can always go back to the previous point.