Skip to content

Conversation

@clydin
Copy link
Member

@clydin clydin commented Oct 5, 2021

This reverts commit 7bdcd7d.

As of rxjs version 7 (up to and including the current 7.3.1), only the ES5 variant of rxjs can be imported/required when bundling. ES2015 files are available but currently not resolvable via the exports field defined within the package. While the ES5 variant is functional, it can lead to larger application sizes due to the extra code from the ES5 down-leveling process. This unfortunately can also lead to performance regressions with newly created applications (or applications that transition to v7) both by being larger and needing to execute more (down-leveled) code at application runtime. As a result, Angular’s current recommendation is to use rxjs version 6 to prevent performance regressions within Angular applications. Once these issues have been resolved and the ES2015 code is available for use, the new project default can be updated to use version 7 but that change is limited to only major versions of Angular.
One potential solution is the following PR: ReactiveX/rxjs#6614

This reverts commit 7bdcd7d.

As of `rxjs` version 7 (up to and including the current 7.3.1), only the ES5 variant of `rxjs` can be imported/required when bundling. ES2015 files are available but currently not resolvable via the `exports` field defined within the package. While the ES5 variant is functional, it can lead to larger application sizes due to the extra code from the ES5 down-leveling process. This unfortunately can also lead to performance regressions with newly created applications (or applications that transition to v7) both by being larger and needing to execute more (down-leveled) code at application runtime. As a result, Angular’s current recommendation is to use `rxjs` version 6 to prevent performance regressions within Angular applications. Once these issues have been resolved and the ES2015 code is available for use, the new project default can be updated to use version 7 but that change is limited to only major versions of Angular.
@clydin clydin added the target: major This PR is targeted for the next major release label Oct 5, 2021
@google-cla google-cla bot added the cla: yes label Oct 5, 2021
@dgp1130 dgp1130 added this to the v13 Feature Freeze milestone Oct 6, 2021
@clydin clydin removed this from the v13 Feature Freeze milestone Oct 6, 2021
@clydin
Copy link
Member Author

clydin commented Oct 6, 2021

Closing as the proposed upstream fix as been merged.

@clydin clydin closed this Oct 6, 2021
@clydin clydin added target: major This PR is targeted for the next major release and removed state: blocked target: major This PR is targeted for the next major release labels Oct 6, 2021
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Nov 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

target: major This PR is targeted for the next major release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants