Closed juristr closed 4 years ago
When updating to a release version it is recommended to use the --next
flag.
ng update @angular/core @angular/cli --next
This is because there are a couple of differences between @next
and --next
.
The main being that that @next
will only use the next
npm tag of the package provided. While --next
will use also update to the latest prerelease version of the CLI to perform the update and peerDependencies matching will include pre-release versions, which otherwise you'd need to use the --force
to suppress the warnings and continue with the update.
Note: The aot
option should not be added under dev-server
but rather under build -> options
, because the builder builder options will be used unless overridden in the dev-server options.
Awesome, make sense. Thx for debugging π
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.
π Bug report
Command (mark with an
x
)Is this a regression?
No, it's not a regression since this is something new that is supposed to change with Ivy.
Description
After the
ng update
command I expect that my projects in theangular.json
have theaot
flag set totrue
, not just for the production configuration, but also for the dev server.π¬ Minimal Reproduction
Using node
v12.4.0
and using yarn as my package manager (it's configured globally s.t. also theng update
command picks it up properly).Commands run:
The only change to the
angular.json
is the addition of the budgets sectionπ Your Environment