Closed rof20004 closed 7 years ago
Sounds like you have permissions issues with your global node_modules.
https://docs.npmjs.com/getting-started/fixing-npm-permissions
This isn't a problem with this package, so I'm going to close this.
Hi, sorry for a little information, in fact, I discovered that when I install reaction-cli, I do not sure, but seems it install inside heroku: /use/local/heroku/bin/reaction
Is this right?
No, that doesn't look right. I just installed it on a fresh instance of Debian Stretch and it installed in /usr/lib/node_modules/reaction-cli
and added a symlink for the executable to /usr/bin/reaction
.
Are you trying to run this on Heroku? If so, that's not how reaction-cli
is intended to be used. It's a tool for local development. You don't usually run it on remote servers.
Are you just trying to start up a shop or are you actually writing custom code?
No, my Debian Stretch is an fresh update of Debian Jessie, I just used yarn global add reaction-cli and only worked for root, thanks for answer, I will investigate.
If it only works for root, then my first answer is the solution. You need to change permissions of the global node_modules directory to be owned by your non-root user.
I will investigate, because all my other npm modules working normal, I have vue-cli, firebase, etc.
In my O.S Debian Stretch 9 64 bits, when I run;
npm install -g reaction-cli
this install only for root, not for all users.
I tried too:
yarn global add reaction-cli
and not working too.