I'm trying to understand the flow of installing a new package. I run npm i <package> and the package is installed in node_modules. Then, if I follow with npm i then gpm will kick in and create the flat dirs. Now we have duplication of packages in node_modules and in the dir above. Is the idea when we deploy, we delete/ignore node_modules?
Another problem is if I want to remove a package, npm uninstall <package> then it removes from node_modules, but all the flat dirs are left — so then all of those would have to be rooted out manually I guess... I suppose that's being nit-picky for the intent, on the other hand, the management doesn't seem scalable even for a relatively small app because well, js library deps...
I DO really like the testing setup though!
RE: Isomorphic (ES6 + Node.JS) Module Boilerplate W/ Universal Testing