|
I found another issue which results to build failure:
if you kill the build when npm is running, it may result to something like this:
[INFO] --- frontend-maven-plugin:0.0.16:grunt (grunt build) @ unifiedpush-admin-ui ---
[INFO] Running 'grunt dist --no-color' in /Users/lukasfryc/Documents/workspace/aerogear-unifiedpush-server/admin-ui
[INFO]
[INFO] module.js:340
[INFO] throw err;
[INFO] ^
[INFO] Error: Cannot find module 'findup-sync'
[INFO] at Function.Module._resolveFilename (module.js:338:15)
[INFO] at Function.Module._load (module.js:280:25)
[INFO] at Module.require (module.js:364:17)
[INFO] at require (module.js:380:17)
[INFO] at Object.<anonymous> (/Users/lukasfryc/Documents/workspace/aerogear-unifiedpush-server/admin-ui/node_modules/grunt-cli/bin/grunt:8:14)
[INFO] at Module._compile (module.js:456:26)
[INFO] at Object.Module._extensions..js (module.js:474:10)
[INFO] at Module.load (module.js:356:32)
[INFO] at Function.Module._load (module.js:312:12)
[INFO] at Function.Module.runMain (module.js:497:10)
the problem here is inconsistent node_modules/.
So cleaning node_modules/ helped.
But then, the NPM cache itself was broken:
[INFO] --- frontend-maven-plugin:0.0.16:npm (npm install) @ unifiedpush-admin-ui ---
[INFO] Running 'npm install --color=false' in /Users/lukasfryc/Documents/workspace/aerogear-unifiedpush-server/admin-ui
[INFO] npm WARN package.json ups-admin-ui@0.0.0 No repository field.
[INFO] npm ERR! cb() never called!
[INFO] npm ERR! not ok code 0
Now we have to refresh the cache (we would normally do that using npm clean cache but the build has local cache to avoid conflicts in global cache).
|
