-
Notifications
You must be signed in to change notification settings - Fork 6
Open
Description
Following instructions from README, npm install fails with Failed at the runtimejs@0.2.14 postinstall script 'node scripts/update-versions.js':
Env:
# npm -v
4.4.1
root@ubuntu:~/runtime.js/helloworld# nodejs -v
v6.10.0
helloworld# ls
index.js package.json README.md
Output:
root@ubuntu:~/runtime.js/helloworld# npm install
> runtimejs@0.2.14 postinstall /root/runtime.js/helloworld/node_modules/runtimejs
> node scripts/update-versions.js
module.js:472
throw err;
^
Error: Cannot find module '/root/runtime.js/helloworld/node_modules/runtimejs/scripts/update-versions.js'
at Function.Module._resolveFilename (module.js:470:15)
at Function.Module._load (module.js:418:25)
at Module.runMain (module.js:605:10)
at run (bootstrap_node.js:422:7)
at startup (bootstrap_node.js:143:9)
at bootstrap_node.js:537:3
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! runtimejs@0.2.14 postinstall: `node scripts/update-versions.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the runtimejs@0.2.14 postinstall script 'node scripts/update-versions.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the runtimejs package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node scripts/update-versions.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs runtimejs
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls runtimejs
npm ERR! There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2017-03-15T21_09_53_252Z-debug.log
Attempt at following README from Runtime repo also landed at the same error (Failed at the runtimejs@0.2.14 postinstall script 'node scripts/update-versions.js'.):
/root/runtime.js/project# npm install runtimejs --save
> runtimejs@0.2.14 postinstall /root/runtime.js/project/node_modules/runtimejs
> node scripts/update-versions.js
module.js:472
throw err;
^
Error: Cannot find module '/root/runtime.js/project/node_modules/runtimejs/scripts/update-versions.js'
at Function.Module._resolveFilename (module.js:470:15)
at Function.Module._load (module.js:418:25)
at Module.runMain (module.js:605:10)
at run (bootstrap_node.js:422:7)
at startup (bootstrap_node.js:143:9)
at bootstrap_node.js:537:3
npm WARN test@1.0.0 No description
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! runtimejs@0.2.14 postinstall: `node scripts/update-versions.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the runtimejs@0.2.14 postinstall script 'node scripts/update-versions.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the runtimejs package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node scripts/update-versions.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs runtimejs
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls runtimejs
npm ERR! There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2017-03-15T21_17_31_579Z-debug.log
Snippet from debug log (/root/.npm/_logs/2017-03-15T21_17_31_579Z-debug.log):
2975 verbose lifecycle runtimejs@0.2.14~postinstall: CWD: /root/runtime.js/project/node_modules/runtimejs
2976 silly lifecycle runtimejs@0.2.14~postinstall: Args: [ '-c', 'node scripts/update-versions.js' ]
2977 silly lifecycle runtimejs@0.2.14~postinstall: Returned: code: 1 signal: null
2978 info lifecycle runtimejs@0.2.14~postinstall: Failed to exec postinstall script
2979 verbose unlock done using /root/.npm/_locks/staging-6489a859f817d055.lock for /root/runtime.js/project/node_modules/.staging
2980 silly rollbackFailedOptional Starting
Is the latest runtime.js version (0.2.14) stable? Looked through open/closed issues, but could not find above symptom being encountered before. If 0.2.14 is not stable, can you please recommend a stable version to try out? Thanks a lot!
Metadata
Metadata
Assignees
Labels
No labels