-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[Planned] adjust transpilation target above es5 #5270
Labels
8.x
Issues and PRs for version 8.x
Comments
kwonoj
changed the title
[Discussion] adjust transpilation target above es5
[Planned] adjust transpilation target above es5
Feb 3, 2020
Core team has reached general agreement to pursue this. Current planned roadmap as written below, still subject to change depends on ecosystem / user feedback.
|
kwonoj
added a commit
that referenced
this issue
Apr 30, 2021
- relates to #5270 BREAKING CHANGES: cjs, esm output targets ES2015 syntax, drop IE11 support
This was referenced Apr 30, 2021
benlesh
added
8.x
Issues and PRs for version 8.x
AGENDA ITEM
Flagged for discussion at core team meetings
labels
May 4, 2021
4 tasks
Looks like right now, v8 will ship |
Yes, that's the plan so far. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is definitely semver major breaking changes discussion.
With Windows 7 EOL, IE11 is also considered as EOL. There are still in-use customers like few enterprise companies, but it won't get a major update in features at all.
Currently, rxjs targets transpilation target's set to
es5
, conservative runtime output to support most of browsers. This issue is to discussThis depends on major browser usage across consumers, but probably best is set to ES2015 to aim conservative target (again).
Consumer aims to make application to use those browser may need additional configuration on their bundler to downlevel transpilation to rxjs.
Maybe not, just open for discussion (in related with native esm support changes I'm trying to tackle).
The text was updated successfully, but these errors were encountered: