Jay, trying to remember...

npm: One tool to rule them all...

After trying to sort out what a toolset should be for standard JS / HTML / possibly Node development, I’m narrowing on just using npm. Here’s the reference material that got me to this place:

npm as front-end package management (bower replacement)

npm as build tool (grunt / gulp replacement)

What I’ve found so far is that I’ve had to install more npm packages that I thought I would- these are to make up for npm’s shortcomings in running scripts. Mostly I can see how this would be a huge pain if I were dev-ing on Windows (which I hopefully never will).

Here’s a link to the package.json file that I’m playing with now - it’s mostly based on the package.json file in this project.

So, lets see if it works without too many weird hoops…


comments powered by Disqus