SebastianVerified account

Also, would you always choose to go with CommonJS over UMD? (I've chosen CommonJS2 but wasn't really sure of the diff from CommonJS!)

@anatomic personally, I'd go with publishing modules in node-style commonJS to npm with deps in package.json. Bundling is for the consumer

@glenathan would always do that but am using quite a few es6 features & require babel transpiling. have previously babeled individual files

@anatomic ah, I see. Babelling all files in a dir makes the most sense imo. I've been avoiding ES6 in libs so far so not had to solve this

@glenathan yeah, keeps the footprint the same but makes dev more painful. Just bundled a package as it was intended to be one entry point

@anatomic I don't follow, how is dev more painful?

@glenathan also stack traces don't match up to original files and it's harder to read the built code if you hit issues

@anatomic you could add a require(lib/dev) which does babel/register perhaps? Maybe @sebmck has some suggestions :)