-
Notifications
You must be signed in to change notification settings - Fork 12k
feat(@angular/cli): build only the projects of a certain type #10397
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
Conversation
Heya @noelmace I talked a bit about this problem in angular/devkit#730 (comment), and at the end of my comment I mention this PR and why I think it is not the right approach to this problem at the moment. Let me know what you think. |
@filipesilva Thanks for this feedback. We continued to speak (a lot) about this in #730, and I think I see now how we could proceed. Please, see if you can add some feedbacks on angular/devkit#730 (comment). On the other hand, I still think this option could be relevant for a more restricted use case : we have some set on libraries as a whole, like For my use case especially, we could also add a --scope option which would permit to just run build targets for projects of a given npm scope / |
This commit is just a first example for angular#10369, following the discussion started in angular/devkit#730. angular/devkit#739 would be needed. This example would also require some evolutions on @angular-devkit/architect, but I'm sure there is a way to do this.
Heya I brought this up with the team and we don't want to do it via filtering through project type. We feel it is a fairly limited way of doing this. The need for this sort of thing is still there in the cases you mentioned. I have made #11002 to track this. There's other parties with similar needs and we hope to converge on a design that satisfies them. |
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. |
Goal feature
Permit to run some architect commands only on projects with a specific projectType.
For example, this will only build the libraries :
angular/devkit#739 would be needed for filtering project names.
Purpose
Applications and libraries doesn't share the same use-cases : where applications are built (thanks to the build-angular build architect) in order to be served through HTTP, libraries, on the other hand, are bundled by ng-packagr in order to be published to a npm repository. Therefore, deployment / publication processes diverged between the two, so is the CI.
This PR is also a first example of angular/devkit#739 use.