jsnext

[salzhrani]

we ran into an issue similar to this
and It seems that jsnext:main entry should to transpiled code that has module syntax, not es6 code. currently the code in lib is es6 and it makes safari sad.

[stefanpenner]

and It seems that jsnext:main entry should to transpiled code that has module syntax, not es6 code. currently the code in lib is es6 and it makes safari sad.

I don't believe that is the point of jsnext:main

[salzhrani]

It is what bundlers like webpack and rollup are expecting.

ref:
reduxjs/redux#1042
jsforum/jsforum#5

[stefanpenner]

jsforum/jsforum#5

doesn't actually come to conclusion, as it is a proposal to reclaim the property for this meaning, and one of the last points raised is: jsforum/jsforum#5 (comment)

---

@Rich-Harris @caridy whats-up with with jsnext:main referring to ES2015 modules only subset of jsnext? Something smells very fishy about that. modules:main or something makes sense.

Also based on the above reading it is essentially locked to something even more restrictive as future additions to the modules syntax would break existing tooling. Does that mean, it is more like es2015-modules:main ?

For whatever it is worth, on our side, we have always treated jsnext main entry points as requiring a full transpile.

[stefanpenner]

3.4.0 now points to a bundle with only exports statements: 28e5753