Because having a mix of libraries/modules which some export defaults and some don't makes it cumbersome to require them here and there: I have to remember which

Because having a mix of libraries/modules which some export defaults and some don't makes it cumbersome to require them here and there: I have to remember which was exported as default and which had the class inside. Also it makes more obvious visually which variables are modules and which are classes/functions. For my projects I avoid default exports even when a module only has one class (which happens frequently). Additionally, ES6 default exports don't mix well with commonJS, sometimes I have to add require('foo').default for no apparent reason. > Also with npm scripts, local deps that expose executables are added to your PATH I think it didn't work reliably on windows or cygwin or something. I just tried and it works everywhere. Good to know! The only gotcha is that ";" and "&&" must have spaces around.