Npm install failed

CesiumJS
1

Hello,

I am trying to build locally, but getting the error:

D:\Cesium\cesium>npm install

cesium@1.134.1 prepare
gulp prepare && husky && node scripts/isCI.js || playwright install --with-deps

[17:22:26] Using gulpfile D:\Cesium\cesium\gulpfile.js
[17:22:26] Starting ‘prepare’…
[17:22:26] ‘prepare’ errored after 6.24 ms
[17:22:26] Error: ENOENT: no such file or directory, copyfile ‘D:\Cesium\cesium\node_modules@zip.js\zip.js\dist\zip-web-worker.js’ → ‘D:\Cesium\cesium\packages\engine\Source\ThirdParty\Workers\zip-web-worker.js’
at copyFileSync (node:fs:3086:11)
at prepare (file:///D:/Cesium/cesium/gulpfile.js:367:3)
at taskWrapper (D:\Cesium\cesium\node_modules\undertaker\lib\set-task.js:13:15)
at bound (node:domain:433:15)
at runBound (node:domain:444:12)
at asyncRunner (D:\Cesium\cesium\node_modules\async-done\index.js:52:18)
at process.processTicksAndRejections (node:internal/process/task_queues:85:11)

my node version is:
node -v
v22.21.0

Do I need to install Zip-Web-Worker independently?

Please advise.

Thanks much,

-Timothy

2

Actually, looking into it more: the following line is not in the dependencies setion of the package.json, so it is not getting copied :frowning:
I added:

“@zip.js/zip.js”: “^2.7.52”,

to my local devDependencies, but this needs to be remedied in the build :slight_smile:

Thanks much,

-Timothy

3

There had been a few hiccups with this dependency in one of the recent versions, but this should be fixed as of @zip.js/zip.js breaking changes and pako version compatability · Issue #12880 · CesiumGS/cesium · GitHub .

Did this happen for a fresh clone of the repo? Or did you update a repo that you already cloned? In the latter case, an
npm update
could resolve it.

4

It was a repo I maintain and keep updated with Cesium Builds (like 3 or 4 times a year) I tried
rm -rf node_modules package-lock.json
npm cache clean --force
npm install

and it did not resolve it. I had to add the devDependencies for @zip.js/zip.js”: “^2.7.52”, to package.json and it worked.

If I see it again, I will do a ‘npm update’ to see if that resolves it, but really npm did not even know about the dependency, so I don’t think that would have worked?

Thanks much!