You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that the interface has completely changed in v6; is there (or will there be) documentation on how to use / migrate to the latest versions of these commands?
Specifically, build and serve have both gone from offering a pretty big set of options (many of which our existing scripts and workflow depend on) to only --configuration and --prod. If --configuration is the replacement for all the options that were removed, it isn't clear from the --help output how it's meant to be used.
Edit: Okay, I think I figured it out. Sets of flags now have to be configured in angular.json, and --configuration references the name of a pre-defined configuration?
In that case, a feature request: the ability to specify a configuration inline (e.g. ng serve --options '{"browserTarget": "cyph.ws:build:dev"}') (and/or just continued backwards compatibility with the 1.x flags).
The text was updated successfully, but these errors were encountered:
It seems that the interface has completely changed in v6; is there (or will there be) documentation on how to use / migrate to the latest versions of these commands?
Specifically,
build
andserve
have both gone from offering a pretty big set of options (many of which our existing scripts and workflow depend on) to only--configuration
and--prod
. If--configuration
is the replacement for all the options that were removed, it isn't clear from the--help
output how it's meant to be used.Edit: Okay, I think I figured it out. Sets of flags now have to be configured in angular.json, and
--configuration
references the name of a pre-defined configuration?In that case, a feature request: the ability to specify a configuration inline (e.g.
ng serve --options '{"browserTarget": "cyph.ws:build:dev"}'
) (and/or just continued backwards compatibility with the 1.x flags).The text was updated successfully, but these errors were encountered: