cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

WebIDE Grunt Build Failing

mahesh_z
Participant
3,418

Hello,

I am getting below error with my project while building it in SAP Web IDE Full Stack - Licensed version. It was working fine till Friday, i was able to build all my projects but seems something is updated from SAP side and now I am getting build errors for all my projects. Please find the error log as follows -

11:40:26 AM (Build) Build started.11:40:30 AM (DIBuild) Build of "/MyProject" in progress.11:40:30 AM (DIBuild) [INFO] Retrieving source code
[INFO] Preparing node environment
11:40:35 AM (DIBuild) [INFO] Node environment ready
11:41:05 AM (DIBuild) [INFO] Installing node dependencies
11:41:11 AM (DIBuild) npm WARN deprecated coffee-script@1.10.0: CoffeeScript on NPM has moved to "coffeescript" (no hyphen)
11:41:32 AM (DIBuild) npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor.
11:41:37 AM (DIBuild) npm ERR! code Z_BUF_ERROR
npm ERR! errno -5
npm ERR! zlib: unexpected end of file

npm ERR! A complete log of this run can be found in:
npm ERR! /mnt/npm_cache/_logs/2018-10-29T01_41_36_031Z-debug.log
11:41:40 AM (DIBuild)
Build failed.
Please follow the relevant troubleshooting tips below:
ERROR: "Unable to find local grunt"
- Right-click the project folder, select "Clean npm Folder", and build again.
ERROR: "npm ERR! code EINTERGITY"
- Delete the "package-lock.json" file from the project and build again.
[INFO] Build finished in 70 seconds

Already deleted package-lock.json and tried again , but no luck with that.

Any urgent help would be really appreciated.

eliranaz

asaf.bruner

Can you guys please help here ?

Thanks ,

Mahesh Zeple.

View Entire Topic
0 Kudos

Hello Guys,

I am also facing the same issue. Any help will be appreciated.

former_member294848
Discoverer
0 Kudos

I am also facing the same issue.

BjrnB
Participant
0 Kudos

Hello,

I am also facing the same issue since today.

alexandruopre
Explorer
0 Kudos

I am also facing this issue starting today.

Did yours get fixed "by itself" back then? If you remember.