Don't assume what's in your node_modules folder

NPM v3 has been out for a little while now, and with it has come a not insignificant change, the structure of the node_modules folder has been largely flattened. If you're just using other modules within your project, then this change shouldn't really impact you. If you're publishing an npm module with dependency on other modules, however, then this change means that the dependencies of your module are likely to be in the root level.

Cleaning up your Gruntfile with hidden subtasks

A Gruntfile can become less-manageable quite easily when there are multiple things wanting to run the same set of tasks. For example, the steps to compile CSS might always be to run sass and then autoprefixer, but this would be both part of the main build task, required as part of any dist task there may be, and then run on watch any time a .scss source file changes.

Notes from #lwssausage

My notes from London Web Standards June Event #lwssausage - Bruce's tour of the sausage factory by Bruce Lawson, and Building awesome responsive experiences with JavaScript by Jonathan Fielding.

Notes from #lwshttp

My notes from London Web Standards March Event #lwshttp - Playlister: Developing a new music product at the BBC by Sara Gonzalo, and What to expect from HTTP/2 from Mark Nottingham.

Notes from #lwslightning

My notes from London Web Standards November Event #lwslightning - Architecting for Success from Daniel Knell, and four lightning-talks by Laura Dawson, Leonard Houx, Fabio Bertone, and Daniel Appelquist.

Converting from LESS to Sass

Initially I fell down on the LESS side of this divide, the main reason being the ease of it. All you have to do is include the javascript file and you're away. Syntactically it's a whole lot easier to use as well, there's almost no extra syntax to learn, and writing custom mixins takes no time at all.