You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 19, 2019. It is now read-only.
I used chocolatey to install node. I then went to install some packaged with npm (using -g global option). Most packages are installed under c:\ProgramData\chocolatey\bin and are available immediately. Examples of packages that are working correctly are grunt-cli, gulp, & yo. When i install bower it gets installed in C:\ProgramData\chocolatey\lib\nodejs.commandline.0.10.33\tools. There was nothing put in c:\ProgramData\chocolatey\bin. Of course it doesn't work because that directory isn't in my path. While i could easily add that to my path i'm thinking that might be a bad idea because as node gets updated there will most likely be a new directory created under _\lib_ with the new version. Is this a chocolatey issue or is this a node/npm issue?
The text was updated successfully, but these errors were encountered:
Ncage1974
changed the title
Issued with Node (npm) & bower?
Issues with Node (npm) & bower?
Dec 8, 2014
I used chocolatey to install node. I then went to install some packaged
with npm (using -g global option). Most packages are installed under
c:\ProgramData\chocolatey\bin and are available immediately. Examples of
packages that are working correctly are grunt-cli, gulp, & yo. When i
install bower it gets installed in
C:\ProgramData\chocolatey\lib\nodejs.commandline.0.10.33\tools. Of course
it doesn't work because that directory isn't in my path. While i could
easily add that to my path i'm thinking that might be a bad idea because as
node gets updated there will most likely be a new directory created under
_\lib_ with the new version. Is this a chocolatey issues or is this a
node/npm issue?
—
Reply to this email directly or view it on GitHub #636.
Thanks Rob that worked. Hopefully in the future there is some better way to figure out what the correct package to install is. I remember having some confusing when first installing git whether to install the "git" package or the "git.install" package. In git case i believe i was told they were the same thing so incorrectly i assumed the *.install packages where always the same thing.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I used chocolatey to install node. I then went to install some packaged with npm (using -g global option). Most packages are installed under c:\ProgramData\chocolatey\bin and are available immediately. Examples of packages that are working correctly are grunt-cli, gulp, & yo. When i install bower it gets installed in C:\ProgramData\chocolatey\lib\nodejs.commandline.0.10.33\tools. There was nothing put in c:\ProgramData\chocolatey\bin. Of course it doesn't work because that directory isn't in my path. While i could easily add that to my path i'm thinking that might be a bad idea because as node gets updated there will most likely be a new directory created under _\lib_ with the new version. Is this a chocolatey issue or is this a node/npm issue?
The text was updated successfully, but these errors were encountered: