Earlier this week, as almost everyone reading this article knows, npm experienced a brief service interruption where npm install would fail for heaps of popular packages …

I’ve been bitten a few times by dependencies using semver ranges such as ^1.0.1 where the dependency introduced a “non-breaking” change that ended …

These are short-form “thoughts”, in addition to the usual longer-form articles in the blog. The goal is to publish one of these every weekday. I’d …

BrowserSync is a browser testing tool, similar to LiveReload. It also synchronizes across browsers and is going to provide HTML injection in the very near future, …

Deciding on a technology is always hard. You don’t want to make commitments you won’t be able to back out of, but eventually you’ll have to make a …

Gulp is a recently spawned streaming build system which shows a lot of promise. It brings a really terse code-base to the table, which you can actually walk through in …

Inspired by the now-outdated post 10 Cool Things You Probably Didn’t Realize npm Could Do from Isaacs, the creator of npm, I set out to give you a few more tips on how to take advantage of this ridiculously well executed package manager.

Creating client-side JavaScript packages is increasingly becoming a painful endeavor. Here’s a potential fix.

Back when I introduced assetify, I mentioned publishing packages on npm is very easy.

The first thing you have to do is identify yourself, create an account on npm:

$ npm …

Client-side asset management reveals a series of issues with Node.JS and npm today:

• Node.JS is just a few years old (it was born in 2009)
• Some areas, such as client-side …