We recently released eslint v9.4.0, which is the first version that uses @eslint/config-array.
npm install here now installs eslint v9.4.0.
Since @eslint/config-array is in this monorepo, and the version satisfies semver range declared in eslint, npm install doesn't install @eslint/config-array from npm in node_modules/eslint/node_modules, but lets eslint use top level node_modules/@eslint/config-array. However, this is a symlink to packages/config-array, which therefore must be built before running eslint.
What changes did you make? (Give an overview)
Added npm run build in the Verify Files job.
Related Issues
Is there anything you'd like reviewers to focus on?
Prerequisites checklist
What is the purpose of this pull request?
Fixes Verify Files job.
In two recent PRs (https://github.com/eslint/rewrite/pull/38 & https://github.com/eslint/rewrite/pull/39), running eslint fails with:
I believe what happens is the following:
@eslint/config-array
.npm install
here now installs eslint v9.4.0.@eslint/config-array
is in this monorepo, and the version satisfies semver range declared ineslint
,npm install
doesn't install@eslint/config-array
from npm innode_modules/eslint/node_modules
, but letseslint
use top levelnode_modules/@eslint/config-array
. However, this is a symlink topackages/config-array
, which therefore must be built before running eslint.What changes did you make? (Give an overview)
Added
npm run build
in the Verify Files job.Related Issues
Is there anything you'd like reviewers to focus on?