-
Notifications
You must be signed in to change notification settings - Fork 156
fix(@angular-devkit/build-angular): support some browser options in dev-server #734
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It'd be nice long-term if this type of functionality could be supported without the repetition of options.
"optimization": { | ||
"type": "boolean", | ||
"description": "Defines the optimization level of the build.", | ||
"default": false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These options cannot have a default, otherwise the default will always override the browser target values.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
Yes, and that's what my other PR that I got carried away with is about; enabling us to walk the schema properly to discover options. Let's not get distracted for 6.0 though and implement |
d7b599a
to
3957323
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just that last point and it LGTM.
@@ -51,6 +51,15 @@ export interface DevServerBuilderOptions { | |||
watch: boolean; | |||
hmrWarning: boolean; | |||
servePathDefaultWarning: boolean; | |||
|
|||
optimization: boolean; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These are all optional now.
…ev-server This will allow people to override some flags from a base browser target, either from the command line or from their serve directly. The options chosen are kinda arbitrary. I simply looked at what made sense. Fix angular/angular-cli#10304
This will allow people to override some flags from a base browser target, either from
the command line or from their serve directly.
The options chosen are kinda arbitrary. I simply looked at what made sense.
Fix angular/angular-cli#10304