Skip to content
This repository has been archived by the owner on Feb 19, 2019. It is now read-only.

Issues with Node (npm) & bower? #636

Open
Ncage1974 opened this issue Dec 8, 2014 · 2 comments
Open

Issues with Node (npm) & bower? #636

Ncage1974 opened this issue Dec 8, 2014 · 2 comments

Comments

@Ncage1974
Copy link

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?

@Ncage1974 Ncage1974 changed the title Issued with Node (npm) & bower? Issues with Node (npm) & bower? Dec 8, 2014
@ferventcoder
Copy link
Contributor

You are using an older npm. It is now bundled with Msi and newer versions
are not released separately. Suggest you install nodejs.install instead.

On Monday, December 8, 2014, Ncage1974 [email protected] wrote:

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.

Rob
"Be passionate in all you do"

http://devlicio.us/blogs/rob_reynolds
http://ferventcoder.com
http://twitter.com/ferventcoder

@Ncage1974
Copy link
Author

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants