You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Multiple packages referenced by the projects package.json are old or very old.
This causes not only potential security issues for projects referencing this package it also causes a lot of warnings when installing building and/or bundling this package or packages dependent on this.
For example node-fetch is still referenced with version 2.7.0, which references the ancient version 5.0.0 of whatwg-url (current 14). Not only are most of these packages not using ESM, yet, they are also using deprecated syntax such as "./" or "./*" or "//" exports, deprecated and warned in DEP0155 and DEP0166.
Some packages like devcert can be replaced with native Node Crypto implementations (I'm not sure if devcert is even used)
Multiple packages referenced by the projects package.json are old or very old.
This causes not only potential security issues for projects referencing this package it also causes a lot of warnings when installing building and/or bundling this package or packages dependent on this.
For example
node-fetch
is still referenced with version 2.7.0, which references the ancient version 5.0.0 ofwhatwg-url
(current 14). Not only are most of these packages not using ESM, yet, they are also using deprecated syntax such as "./" or "./*" or "//" exports, deprecated and warned in DEP0155 and DEP0166.Some packages like devcert can be replaced with native Node Crypto implementations (I'm not sure if devcert is even used)
Here is the current status of dependencies:
The text was updated successfully, but these errors were encountered: