Skip to content

fix(@angular-devkit/build-angular): only set ngDevMode when script optimizations are enabled #24421

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

Merged
merged 1 commit into from
Dec 13, 2022

Conversation

clydin
Copy link
Member

@clydin clydin commented Dec 12, 2022

When using the experimental esbuild-based browser application builder, the ngDevMode global runtime variable was unintentionally always being set to false due to a previous bug fix that stopped the variable from being replaced with the value of true when script optimizations were disabled. By doing so, the fix caused the imported compiler-cli GLOBAL_DEFS_FOR_TERSER_WITH_AOT constant to take precedence which contains an ngDevMode value of false. To prevent this situation for development builds where a non-false ngDevMode is helpful to surface potential runtime problems, GLOBAL_DEFS_FOR_TERSER_WITH_AOT will no longer change the value of ngDevMode. This fix does not have any effect on production builds since ngDevMode would have been set to false regardless.

…timizations are enabled

When using the experimental esbuild-based browser application builder, the `ngDevMode` global
runtime variable was unintentionally always being set to false due to a previous bug fix that stopped
the variable from being replaced with the value of true when script optimizations were disabled.
By doing so, the fix caused the imported compiler-cli `GLOBAL_DEFS_FOR_TERSER_WITH_AOT` constant
to take precedence which contains an `ngDevMode` value of false. To prevent this situation for
development builds where a non-false `ngDevMode` is helpful to surface potential runtime problems,
`GLOBAL_DEFS_FOR_TERSER_WITH_AOT` will no longer change the value of `ngDevMode`. This fix does not
have any effect on production builds since `ngDevMode` would have been set to false regardless.
@clydin clydin added the target: patch This PR is targeted for the next patch release label Dec 12, 2022
@clydin clydin requested a review from alan-agius4 December 12, 2022 22:00
@clydin clydin added the action: review The PR is still awaiting reviews from at least one requested reviewer label Dec 12, 2022
@alan-agius4 alan-agius4 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 Dec 13, 2022
@angular-robot angular-robot bot merged commit 310144d into angular:main Dec 13, 2022
@clydin clydin deleted the esbuild/fix-ngDevMode branch December 13, 2022 14:28
@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 Jan 13, 2023
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 target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants