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

Deprecated npm packages #1538

Open
c4chale opened this issue Dec 20, 2022 · 4 comments
Open

Deprecated npm packages #1538

c4chale opened this issue Dec 20, 2022 · 4 comments

Comments

@c4chale
Copy link

c4chale commented Dec 20, 2022

Upon installation I did recieved a lot of warning about deprecated npm packages.

This is the output i received:

npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '^12 || ^14 || ^16' },
npm WARN EBADENGINE   current: { node: 'v18.12.1', npm: '8.19.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '@es-joy/[email protected]',
npm WARN EBADENGINE   required: { node: '^12 || ^14 || ^16' },
npm WARN EBADENGINE   current: { node: 'v18.12.1', npm: '8.19.2' }
npm WARN EBADENGINE }
npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-url#deprecated
npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated [email protected]: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
npm WARN deprecated @stylelint/[email protected]: Use the original unforked package instead: postcss-markdown
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated @npmcli/[email protected]: This functionality has been moved to @npmcli/fs
npm WARN deprecated [email protected]: Use your platform's native performance.now() and performance.timeOrigin.
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated [email protected]: some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added
npm WARN deprecated [email protected]: This SVGO version is no longer supported. Upgrade to v2.x.x.
npm WARN deprecated [email protected]: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.

added 1588 packages, and audited 1589 packages in 4m

219 packages are looking for funding
  run `npm fund` for details

11 vulnerabilities (3 moderate, 8 high)
@dhananjaygbhardwaj
Copy link

I got the same warnings while setting up the project a few months ago. I was gonna raise the issue, however, I choose to ignore because I am not using the specific packages, but someone might want to use them. Kudos for posting this!

@webletm
Copy link

webletm commented Jan 30, 2024

Yes I'm starting to get the same errors is vscode now. I tried updating @wordpress/scripts in hope that it would update stylelint and I'm just getting incompatibility errors.

@zkmark
Copy link

zkmark commented Apr 23, 2024

Yes I'm starting to get the same errors is vscode now. I tried updating @wordpress/scripts in hope that it would update stylelint and I'm just getting incompatibility errors.

did you manage to solve it?

@dhananjaygbhardwaj
Copy link

@zkmark Tried updating the NPM packages in package.json?

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

4 participants