Introduction to npm as a Build Tool

The Node Package Manager (npm) and the package.json file in combination makes a great option for build automation. Using npm and package.json is simpler and has no extra dependencies such as Gulp and Grunt for example. It's easy to get started by moving your existing commands into the package.json and you can utilize the entire Node package library in your script.
Course info
Rating
(175)
Level
Beginner
Updated
October 21, 2015
Duration
1h 37m
Table of contents
Description
Course info
Rating
(175)
Level
Beginner
Updated
October 21, 2015
Duration
1h 37m
Description

Why should I even care about this when there's an abundance of great tools already? npm is baked into your process already. No build tools are needed and any command you run at the command prompt today can be moved into your package.json with one line of code. The Node package library, that you most likely are using anyway, is vast and contains just about anything you need for your automation. Keeping it in npm and package.json means that everyone can use it. No additional configuration is needed. Just npm install and then use the scripts. You now only have one place to keep updated.

About the author
About the author

Get agile to work in practice - is my motto. This had led me to take interest in all kinds of things: Lean, TDD, Kanban, Specification by example, Node, Continuous Deliver, Nancy and Koa.

More from the author
io.js and Node.js Next: Getting Started
Intermediate
42m 56s
4 Jun 2015
Introduction to Koa Javascript
Intermediate
2h 3m
12 Dec 2014