Skip to Content
0

WebIDE Full-Stack build fails with ENOENT: no such file or directory

Apr 09 at 01:43 PM

74

avatar image

Migrated an app from "normal" WebIDE to the full-stack version. Kept on developing and also building and deoploying. But since today I am receiving errors whenever I try to build.

A lot of "no such file or directory" warnings:

pm WARN tar ENOENT: no such file or directory, open '/tmp/webide.rVa.build/proj/node_modules/.staging/lodash-1759bc25/differenceBy.js'npm WARN tar ENOENT: no such file or directory, open '/tmp/webide.rVa.build/proj/node_modules/.staging/lodash-1759bc25/zipWith.js'npm WARN tar ENOENT: no such file or directory, open '/tmp/webide.rVa.build/proj/node_modules/.staging/lodash-1759bc25/differenceWith.js'

And finally:

npm ERR! code EINTEGRITY
npm ERR! Verification failed while extracting grunt-contrib-clean@1.1.0:
npm ERR! sha1-Vkq/LQN4qYOhW54/MO51tzjEBjg= integrity checksum failed when using sha1: wanted sha1-Vkq/LQN4qYOhW54/MO51tzjEBjg= but got sha512-z4PhNX7vuL3xVChQ1m2AB9Yg5AULVxXcg/SpIdNs6c5H0NE8XYXysP+DGNKHfuwvY7kxvUdBeoGlODJ6+SfaPg== sha1-2jmj7l5rSw0yVb/vlWAYkK/YBwk=. (0 bytes)

Any ideas?

10 |10000 characters needed characters left characters exceeded

Hi,

Same here for me. It suddenly stopped working for no apparent reason. A few hours ago I was able to build my app.

Most errors look like wrong checksums on packages. Deleting package-lock.json did not help. Is there any way to clear npm cache?

0

Hi Lennart,

See me comment to Andreas.

Sorry for the inconvience.

Eliran

0
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Best Answer
Eliran Azuri
Apr 10 at 12:46 PM
0

Hi Andreas,

We familiar with this issue and working on fix.

Meanwhile, you can use the following workaround:

1. Build the project locally (npm install)
2. When finished, go to your app and import package-lock.json file.
3. Build again in your app

Build should pass successfully.

Eliran

Share
10 |10000 characters needed characters left characters exceeded