I agree with Tyler Lesperance, this post should be included in the documentation. It would have saved me literally hours and given me a greater understanding of what I was doing with all those commands.
The most important thing I found lacking from any docs anywhere, was that “command line” means the NodeJS command line. It took me most of the set up time trying to do things in either the windows command line or Git bash, and nothing was working for me. Once I noticed that Nodejs had its own, I was off and running (well,almost).
Great post, bookmarking and linking to from my own blog post on Node. Thanks!!
Cindy Dykstra
I agree with Tyler Lesperance, this post should be included in the documentation. It would have saved me literally hours and given me a greater understanding of what I was doing with all those commands.
The most important thing I found lacking from any docs anywhere, was that “command line” means the NodeJS command line. It took me most of the set up time trying to do things in either the windows command line or Git bash, and nothing was working for me. Once I noticed that Nodejs had its own, I was off and running (well,almost).
Great post, bookmarking and linking to from my own blog post on Node. Thanks!!