Tree shaking issue: jsnext:main targets pre-transpiled assets

Hi everyone,

The issue that we are currently having on the team i work is that we were setting everything up on our project for code-splitting and tree shaking with webpack, and we noticed that our build was failing because webpack was trying to load es6 module version based on the jsnext:main attribute, and that particular entry point has not yet being transpiled, making the build process fail.

If possible i'd like to avoid having to manually manage the transpile process of external libraries, and i say manually because not excluding node_modules from the transpile process (which would be the transparent solution) has some serious penalties.

Has anyone else had to play with these?

Cheers!