1. `browser` was added as an intention to ship browser specific builds via npm (along with node.js specific builds) 2. `module` was added as intention to ship modern js (ES2015 aka ES6 or later) ``` main --(1)--> browser | | | | (2) | | | ˅ ˅ module --------> ? ``` As a result, there is obvious hole - how do you deliver modern js for browser specific builds Suggested solutions: - [`module-browse`](https://github.com/webpack/webpack/issues/4674) - [`esm: true`](https://github.com/nodejs/node-eps/pull/60) - [`esnext`](http://2ality.com/2017/04/transpiling-dependencies-babel.html) Related: - [Draft ES Module Interoperability](https://github.com/nodejs/node-eps/blob/master/002-es-modules.md) - [In Defense of .js](https://github.com/dherman/defense-of-dot-js/blob/master/proposal.md) - [es-module-loader](https://github.com/ModuleLoader/es-module-loader) - [reify](https://github.com/benjamn/reify)
browserwas added as an intention to ship browser specific builds via npm (along with node.js specific builds)modulewas added as intention to ship modern js (ES2015 aka ES6 or later)As a result, there is obvious hole - how do you deliver modern js for browser specific builds
Suggested solutions:
module-browseesm: trueesnextRelated: