"@wordpress/scripts" seems to be incompatible with "node v20.x".

[stein2nd]

Description

I report that I ran "npm install @wordpress/scripts --save-dev" and got the following WARN.:

npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '^14 || ^16 || ^17 || ^18 || ^19' },
npm WARN EBADENGINE current: { node: 'v20.5.0', npm: '9.8.0' }
npm WARN EBADENGINE }

npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@es-joy/[email protected]',
npm WARN EBADENGINE required: { node: '^14 || ^16 || ^17 || ^18 || ^19' },
npm WARN EBADENGINE current: { node: 'v20.5.0', npm: '9.8.0' }
npm WARN EBADENGINE }

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

When I ran "npm install -D eslint eslint-plugin-jsdoc @es-joy/jsdoccomment" individually, no warn showed up.

Step-by-step reproduction instructions

1. Using Terminal, run "npm install -D @wordpress/scripts".

Screenshots, screen recording, code snippet

No response

Environment info

• Device: macOS Ventura 13.5

Please confirm that you have searched existing issues in the repo.

Yes

Please confirm that you have tested with all plugins deactivated except Gutenberg.

No

[stein2nd]

Additional information (2023-08-02 11:47 JST).

• Below are the versions of "eslint-plugin-jsdoc" and "@es-joy/jsdoccomment" when installed individually:

  • eslint-plugin-jsdoc: 46.4.5
  • @es-joy/jsdoccomment: 0.39.4

• The following is the result of running "npm ls stable":

  • └─┬ @wordpress/[email protected]
    • └─┬ @svgr/[email protected]
      • └─┬ @svgr/[email protected]
        • └─┬ [email protected]
          • └── [email protected]

[stein2nd]

When [email protected] was installed separately, the "deprecated [email protected]" warning did not appear.

In other words, maybe @wordpress/scripts should install @svgr/[email protected] instead of @svgr/[email protected].

[stein2nd]

• The following is the result of running "npm ls eslint-plugin-jsdoc":

  • ├─┬ @wordpress/[email protected]
    • │ └─┬ @wordpress/[email protected]
      • │ └── [email protected]
  • └── [email protected] <- manual installed

• Next, the following is the result of running "npm ls @es-joy/jsdoccomment":

  • ├── @es-joy/[email protected] <- manual installed
  • ├─┬ @wordpress/[email protected]
    • │ └─┬ @wordpress/[email protected]
      • │ └─┬ [email protected]
        • │ └── @es-joy/[email protected]
  • └─┬ [email protected] <- manual installed
    • └── @es-joy/[email protected] deduped

Therefore, maybe @wordpress/eslint-plugin should install [email protected] instead of [email protected].

[mikeybinns]

I am also running into this issue with @es-joy/jsdoccomment, and it seems like eslint-plugin-jsdoc in eslint-plugin is the way to fix it for me

[gziolo]

I opened #53629 which tries to fix the issue with eslint-plugin-jsdoc.

[gziolo]

I also opened #53630 to see what's required to get rid of the deprecated [email protected] deep dependency.