fix(@angular/cli): strip decorators with Angular 5+ #8077
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The releases that include this PR should update |
filipesilva
force-pushed
the
build-opt-default-true
branch
from
09e79ad to
240f0be
Compare
filipesilva
force-pushed
the
build-opt-default-true
branch
from
240f0be to
49df5fa
Compare
We feel build This PR defualts `build-optimizer` when using Angular 5+ on a production build with `--aot`. It can still be turned off with `--no-build-optimizer` (or `--build-optimizer=false`). Fix angular#8050
filipesilva
force-pushed
the
build-opt-default-true
branch
from
49df5fa to
d764518
Compare
hansl
approved these changes
Oct 18, 2017
filipesilva
added a commit
that referenced
this pull request
Oct 18, 2017
We feel build `--build-optimizer` is stable enough to not be experimental anymore. This PR defaults `build-optimizer` when using Angular 5+ on a production build with `--aot`. It can still be turned off with `--no-build-optimizer` (or `--build-optimizer=false`). Fix #8050
filipesilva
added a commit
to filipesilva/angular-cli
that referenced
this pull request
Oct 24, 2017
filipesilva
added a commit
to filipesilva/angular-cli
that referenced
this pull request
Oct 24, 2017
dond2clouds
pushed a commit
to d2clouds/speedray-cli
that referenced
this pull request
Apr 23, 2018
We feel build `--build-optimizer` is stable enough to not be experimental anymore. This PR defaults `build-optimizer` when using Angular 5+ on a production build with `--aot`. It can still be turned off with `--no-build-optimizer` (or `--build-optimizer=false`). Fix angular#8050
dond2clouds
pushed a commit
to d2clouds/speedray-cli
that referenced
this pull request
Apr 23, 2018
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
We feel build
--build-optimizeris stable enough to not be experimental anymore.This PR defualts
build-optimizerwhen using Angular 5+ on a production build with--aot.It can still be turned off with
--no-build-optimizer(or--build-optimizer=false).Fix #8050