npm ci fails because package-lock is missing optional fsevents entry

[bozicovichsantiago20-oss]

Summary

A clean npm ci fails on the current master branch because package-lock.json is missing the optional node_modules/fsevents entry required by the dependency tree.

Reproduction

git clone --depth 1 https://github.com/Ontotext-AD/graphdb.js.git
cd graphdb.js
npm ci --ignore-scripts --no-audit --no-fund

Actual behavior

npm ci aborts before installing packages:

npm error code EUSAGE
npm error `npm ci` can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync.
npm error Missing: fsevents@2.3.3 from lock file

Expected behavior

npm ci should install from the committed lockfile. This matters because Jenkinsfile runs npm ci in the Install stage.

Fix pointer

Running the lockfile refresh command below adds the missing optional node_modules/fsevents metadata and then npm ci succeeds:

npm install --package-lock-only --ignore-scripts --no-audit --no-fund
npm ci --ignore-scripts --no-audit --no-fund

The resulting diff is only package-lock.json, adding the node_modules/fsevents entry.

Environment

• Repository commit tested: 988c5b630cc340c311115cc8132fa723ff680caa
• Node: v24.16.0
• npm: 11.13.0
• OS: Windows 11 / PowerShell