-
Notifications
You must be signed in to change notification settings - Fork 441
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecated es6 and es6-global in favor of esmodule #6709
Conversation
For reference
The most accurate term is simply |
@cknitt Can this be included in v11.1 rc? if we have no more v11.x after that |
Personally I would have preferred to not add any more new features, bigger changes or deprecations to the 11.1 rcs as we are very close to the release already. But I understand that you want to get the deprecation in now to prepare for removal of the deprecated settings in v12. |
I'm a bit on the fence about this, but since we plan no more 11 releases after this then sure, let's merge it. |
@cometkim can you update the branch? Then ready to merge. Also, please update all relevant docs, so people don't get confused. |
@zth done! |
In v11.x, we only print a deprecation warning for
"es6"
and"es6"
usage and notice to use"esmodule"
In v12
"es6"
and "es6-global" completely, and redirect related output paths (lib/js
tolib/cjs
,lib/es6
tolib/mjs
or we can just merge it into singlelib/js
)"esmodule"
, the standard format will be the default output format."es6-global"