Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
npm install -g mermaid does not install phantomjs
See original GitHub issueOn OS X, if you do a npm install -g mermaid, it will install (0.5.8) but when you try to run it with an imput file you will get an error complaining about Could not find phantomjs at the specified path.
Please note that this error appears only if you give a file to process. If you do just mermaid -v it will return the version without the error.
Issue Analytics
- State:
- Created 8 years ago
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Could not find phantomjs at the specified path - Stack Overflow
I solve this problem. I noticed that， if you install phantomjs by this npm -g install phantomjs , actually it is wrong, and...
Read more >phantomjs - npm
phantomjs. An NPM installer for PhantomJS, headless webkit with JS API. DEPRECATED. Pre-2.0, this package was published to NPM as phantomjs.
Read more >mermaid CLI - UNPKG
Installing mermaid globally ( npm install -g mermaid ) will expose the mermaid command to your environment, allowing you to generate PNGs from...
Read more >Changelog - Mermaid zh-cn doc - Hello Wac
Notes: Only site owners can use the mermaidAPI.initialize call, to set values. ... npm install -g mermaid does not install phantomjs #329 ......
Read more >grunt-mermaid - npm Package Health Analysis | Snyk
This is a small grunt plugin that can generate diagram from files with Mermaid syntax. Getting started. Install this plugin next to your...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I see no reason why an upgrade should be hard!
It does seem like you have som issue with your node installation though. I have never had problems with node 1.9. I personally use nvm to install node so that it is easy to upgrade to newer node versions:
https://github.com/creationix/nvm
This should be sone however.
I am not able to replicate the same problem with version 6.0.0 so I am closing this ticket.