Skip to content

fix(core): workaround Terser inlining bug#36200

Closed
filipesilva wants to merge 1 commit intoangular:masterfrom
filipesilva:jit-inline-terser
Closed

fix(core): workaround Terser inlining bug#36200
filipesilva wants to merge 1 commit intoangular:masterfrom
filipesilva:jit-inline-terser

Conversation

@filipesilva
Copy link
Copy Markdown
Contributor

@filipesilva filipesilva commented Mar 23, 2020

This variable name change works around terser/terser#615, which was causing the JIT production tests to fail in the Angular CLI repository (angular/angular-cli#17264).

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • angular.io application / infrastructure changes
  • Other... Please describe:

What is the current behavior?

Issue Number: angular/angular-cli#17264

What is the new behavior?

This variable name change works around terser/terser#615, which was causing the JIT production tests to fail in the Angular CLI repository (angular/angular-cli#17264).

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

@filipesilva filipesilva added the target: major This PR is targeted for the next major release label Mar 23, 2020
@pullapprove pullapprove bot requested review from kara March 23, 2020 13:18
@mary-poppins
Copy link
Copy Markdown

You can preview 7aafe15 at https://pr36200-7aafe15.ngbuilds.io/.

@filipesilva filipesilva added the action: review The PR is still awaiting reviews from at least one requested reviewer label Mar 23, 2020
Copy link
Copy Markdown
Member

@JoostK JoostK left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What a bizarre bug!

Thanks @filipesilva, @clydin and @dgp1130 for the research and fix! 👍

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you include a comment here explaining the bug (maybe link to the Terser issue?) and that the name has to be different?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done, PTAL

This variable name change works around terser/terser#615, which was causing the JIT production tests to fail in the Angular CLI repository (angular/angular-cli#17264).
@alxhub
Copy link
Copy Markdown
Member

alxhub commented Mar 23, 2020

Presubmit

@mary-poppins
Copy link
Copy Markdown

You can preview 2f9163c at https://pr36200-2f9163c.ngbuilds.io/.

Copy link
Copy Markdown
Contributor

@kara kara left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@alxhub alxhub added action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Mar 23, 2020
@mhevery mhevery closed this in 0ce8ad3 Mar 23, 2020
@mhevery mhevery added target: patch This PR is targeted for the next patch release and removed target: major This PR is targeted for the next major release labels Mar 23, 2020
mhevery pushed a commit that referenced this pull request Mar 23, 2020
This variable name change works around terser/terser#615, which was causing the JIT production tests to fail in the Angular CLI repository (angular/angular-cli#17264).

PR Close #36200
@angular-automatic-lock-bot
Copy link
Copy Markdown

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 Apr 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker cla: yes target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants