-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Install fails #33
Comments
Getting Same while installing `> node-plantuml@0.9.0 postinstall C:\MI\node-api-structure-sails\node_modules\node-plantuml
events.js:288 Error: spawn java ENOENT npm ERR! A complete log of this run can be found in: |
Getting the same... Any updates for this issue? |
Same issue as #28 , where @markushedvall explained that it is because you need Java to be installed (and added to path):
I had the same issue on Ubuntu and installing Java resolved it, I suppose it works on Windows too |
i got: Version: 2.9.3 |
On Windows 10 - and I have already installed
Graphviz
and added it to Windows environment system path:npm install node-plantuml
events.js:167
throw er; // Unhandled 'error' event
^
Error: spawn java ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:232:19)
at onErrorNT (internal/child_process.js:407:16)
at process._tickCallback (internal/process/next_tick.js:63:19)
at Function.Module.runMain (internal/modules/cjs/loader.js:745:11)
at startup (internal/bootstrap/node.js:279:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:696:3)
Emitted 'error' event at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:238:12)
at onErrorNT (internal/child_process.js:407:16)
[... lines matching original stack trace ...]
at bootstrapNodeJSCore (internal/bootstrap/node.js:696:3)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! node-plantuml@0.9.0 postinstall:
node scripts/get-vizjs.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-plantuml@0.9.0 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\TB\AppData\Roaming\npm-cache_logs\2020-03-08T08_09_27_242Z-debug.log
The text was updated successfully, but these errors were encountered: