Welcome to the Treehouse Community
Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.
Looking to learn something new?
Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.
Start your free trialjsdevtom
16,963 Points@Jonathan Grieve I learned npm for quite a while and was fairly disappointed that I did because the only commands I've used so far are
-
npm init <module-name>
(Create a package.json file which list the dependencies for the project and your (the owner's information)) -
npm install <module-name>
(just install something) -
npm install <module-name> --save
(install something and save it as a production dependency for the project folder in the file package.json) -
npm install <module-name> --save-dev
(install something and save it as a development dependency for the project folder in the file package.json) -
npm update <module-name>
(self explanatory) -
npm uninstall <module_name>
(self explanatory)
The only thing I would say is be careful with the global flag: -g
.
Otherwise, referring to this cheat sheet for exceptions has covered all of my needs.
Jonathan Grieve
Treehouse Moderator 91,253 PointsJonathan Grieve
Treehouse Moderator 91,253 PointsI am! Thought It may be a while before I get into it because npm basics is a prerequisite course. :-)