Closed thomasfaller closed 6 years ago
I'm not seeing an open issue on this so I'm assuming it might be something on my end with my _PATH or something. I've had issues with Home-brew in the past but it was working ok after I removed it. Any help would still be vastly appreciated 😅
Yeah, seems like an issue with your path
is /Users/tfaller/.npm-packages
and or /Users/tfaller/.npm-packages/lib
in there?
not entirely sure how you have npm set up
Yeah, that's what I thought thanks @ForsakenHarmony I tried pulling out the global path and it gave ne this:
$ npm config get prefix
/Users/tfaller/.npm-packages
$
Does that seems right? So the CLI is being installed in the lib
sub-folder instead of on the main path?
you can check where the executable is located (for me it's in the npm folder, which contains node_modules
) and then see if that folder is in your path
I'm not sure about the lib
sub-folder, it doesn't happen on windows, but might on mac
Thanks.
I added a new directory in my PATH using
export PATH=$PATH:~/.npm-packages/bin
And it seems to be working now, hope this was a good fix 👍
Thanks.
I added a new directory in my PATH using
export PATH=$PATH:~/.npm-packages/bin
And it seems to be working now, hope this was a good fix 👍
I used this command with npm-global
folder and works fine.
If anyone has this folder too, can use.
Thanks!
Thanks.
I added a new directory in my PATH using
export PATH=$PATH:~/.npm-packages/bin
And it seems to be working now, hope this was a good fix 👍
Sorry if commenting after it's closed isn't allowed - but where would you place this command? Is it on a file or do you run it in Terminal?
Hi @jsarge11. Run it on terminal. This command writes on bash file a PATH for bin folder of npm.
export PATH=$PATH:~/.npm-global/bin
works for me.
with yarn
, export PATH=$PATH:~/.yarn/bin
worked for me!
@sarangk-hotstar We don't recommend that you globally install Preact-CLI anymore so you shouldn't be running into this.
What is the current behaviour?
After global installing I get a
command not found
. My code is as follows:I tried both
preact-cli
andpreact-cli@latest
but I get the same message Any thoughts?If the current behaviour is a bug, please provide the steps to reproduce.
Please mention other relevant information.