New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(angular): add support for a custom builder #4903
feat(angular): add support for a custom builder #4903
Conversation
b0e95ab
to
a852a0e
Compare
a852a0e
to
ffafffd
Compare
I think I figured out a better way of doing this. @vsavkin may be looking at the angular one at least. It's just a wrapper around the angular builder. Maybe add a setting. nx.json which would automatically wrap around any build inside workspace.json or angular.json (that's not part of nrwl builders). That way its not as opinionated but you can enable incremental builds. |
@Jordan-Hall thx, I'm going to have a look |
No problem. Happy to produce a prototype on using the nx.json and ensuring any builder can be wrapped by a setting, rather than on builders itself. |
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.
This looks great! 🔥
I've requested a change to the naming of the property to allow it represent the property more accurately.
As another point, however, how does this work with configurations?
Have you tested whether the third party builder receives the configuration object correctly?
For example, an nx build --prod
should then pass the production
configuration object right down to the third party builder.
I'll make the change later today. Yes I've tested this and didn't have any issues. |
ffafffd
to
a255372
Compare
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/nrwl/nx-dev/madebCXeSHvEHJzNZw9pVYxEeiaX [Deployment for 6b8ac39 canceled] |
a255372
to
1eab792
Compare
Ability to support incremental builds when using target builders ISSUES CLOSED: nrwl#4896
1eab792
to
6b8ac39
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.
Thank you! This looks great!
LGTM
This reverts commit a78fe65.
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Ability to support incremental builds when using custom builders
Current Behavior
Currently
@nrwl/angular:webpack-browser
only supports angular builder@angular-devkit/build-angular
. However, this prevents people to use incremental builder when using common builder such as@angular-builders/custom-webpack
Expected Behavior
Ability to use
customBuilder
to overwrite the default angular builder while still support incremental buildsRelated decussion
#4896