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
Installing bs-platform globally fails #2051
Comments
this come from time to time, do you find a work around? maybe we should document it in FAQ |
faced the exact same issue today installing bs-platform globally on Ubuntu 17.04. I'm using sudo, and able to install other packages globally. Tried both on npm 5 and npm 3. update: solved the problem by following the link provided by @bobzhang . Thank you a lot! |
@snaumov so which suggestion did you follow in the link? (I don't have a linux box at hand) |
Thanks for your responses!
I should have added that I executed After following option two of the page @bobzhang mentioned, I fixed this issue:
Maybe it's indeed a good idea to mention this problem in the FAQs. |
Same issue on OSX 10.12.6 , node 8.7.0 and npm 5.4.2 I've uninstalled v8.7 and then installed LTS node-v6.11.4.pkg (where is npm 3.10.10). The same problem is with reason-cli installation: |
Same issue today on the docker node image 8, node 8.9.3 and npm 5.5.1. |
Happens in Docker node image 10: node 10.13.0 and npm 6.4.1, based on Ubuntu. |
This seems to be a common issue, would you mind send a PR to the docs? |
PR sent. This seems to be a general problem, not related to OS or BuckleScript, so I don't know what can be done as yet, but at least now there can be an easy to discover page that gives some suggestions to work around it. |
Thanks, merged! |
Hi and thanks a lot for BuckleScript!
I'm on Arch Linux 4.12.10 using NPM 5.3.0.
Installing bs-platform locally for a project works fine but it fails with the
-g
option:The log file's contents:
Just to make sure that installing globally works in general I executed
npm install -g jquery
. That worked.Thanks and keep up your great work!
The text was updated successfully, but these errors were encountered: