Will/does Webpack support "module" field?

[TehShrike]

To allow importing of ES6 modules with an ES5 module in the package.json's "main" field.

As proposed by rollup.

[IngwiePhoenix]

I +1 this.

Proposed:

• jsnext:main should be within the default list ( https://github.com/webpack/webpack/blob/master/lib/WebpackOptionsDefaulter.js#L83-L88 ) in WebPack2, since it understands ES6 OOTB.

However... Should jsnext:main be treatened in a way that it can't be ignored? Just a thought.

Kind regards,
Ingwie.

[SimenB]

#1612 (comment)

[taion]

Coming from remix-run/react-router#3333, I'd really like if there were a way to specify the location of the ES module build for webpack users.

I'm a little bit frightened that people are importing from the subdirectory containing the ES modules directly.

[rosskevin]

+1 to be a default as @IngwiePhoenix says.

Is there a current way to plugin a resolver to webpack 2 to prefer jsnext:main and otherwise fallback to main? I can currently alter resolve.mainFields (until it is in the default list) but don't we still have to either include that dynamically as part of the src loading?

[TheLarkInn]

@sokra I could take a stab at this if this is as easy as it appears to be.

[taion]

Why do you need a plugin for this? Just set e.g.

mainFields: ['jsnext:main', 'browser', 'main']

in your webpack config.

[rosskevin]

@taion - The problem with this approach is transitive dependencies (or so it seemed when I tried it). I don't think it is as simple as it looks to simply configure or plug-in, it needs to be considered in the primary resolution so that we can take advantage of tree-shaking etc.

[taion]

It works just fine transitively.

[rosskevin]

That is my error in that case; if you have figured it out I'm sure all the participants here would like to see an example of this running.