Also: webpack doesn't care what module load you use. “webpack takes modules with dependencies and generates static assets representing those modules.” http://webpack.github.io/docs/what-is-webpack.html
https://en.wikipedia.org/wiki/Artifact_(software_development) An artifact is one of many kinds of tangible by-products produced during the development of software.
Case study: npm • npm doesn't want you to annoy people who use your package with the details of how you built it. npm package npm registry you publish install
https://www.npmjs.org/doc/misc/npm-scripts.html “The advantage of doing [compilation, transformation, etc] at prepublish time instead of preinstall or install time is that they can be done once, in a single place, and thus greatly reduce complexity and variability.”
https://github.com/Carthage/Carthage “Carthage can automatically use prebuilt frameworks, instead of building from scratch, if they are attached to a GitHub Release on your project’s repository.”