fix(@angular-devkit/build-angular): only set ngDevMode when script optimizations are enabled #24421
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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-cliGLOBAL_DEFS_FOR_TERSER_WITH_AOT
constant to take precedence which contains anngDevMode
value of false. To prevent this situation for development builds where a non-falsengDevMode
is helpful to surface potential runtime problems,GLOBAL_DEFS_FOR_TERSER_WITH_AOT
will no longer change the value ofngDevMode
. This fix does not have any effect on production builds sincengDevMode
would have been set to false regardless.