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.
My notes from Phil Nash's talk at State of the Browser 2015
My notes from Ada Rose Edwards's talk at State of the Browser 2015
My notes from Adam Onishi's talk at State of the Browser 2015
My notes from Laura Elizabeth's talk at State of the Browser 2015
My notes from Bruce Lawson's talk at State of the Browser 2015
My notes from Chris Heilmann's talk at State of the Browser 2015
My notes from Martin Jakl's talk at State of the Browser 2015
My notes from Melinda Seckington's talk at State of the Browser 2015
My notes from Edd Sowden's talk at State of the Browser 2015
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.
My notes from London Web Performance's March event - Responsive and Fast by Michael Gooding and Ellen van Keulen from Akamai.
My notes from Front-end London's January Event - OK Computer from Peter Gasston, Visual Regression Testing from Charlie Owen, and Hackers guide to testing with real users from Tom Alterman.