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
Make affected:libs:build command #2671
Comments
One workaround is to define another target
|
ok i understand what you mean now @vsavkin after reading it in the day time and not middle of the night :/ thats good, but would be a target under a "lib" project in workspace.json only right? I was hoping to do the copy assets as well, as some of our angular libs have assets and that can be done with Node libraries only, Or that is bad design? |
This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if no further activity occurs. |
Possible workaround nx run-many --target=build --projects=$(nx affected:libs --plain | sed 's/ /,/g')
|
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context. |
Expected Behavior
I would like to be able to build affected libs only, not all of them or one by one.
Current Behavior
Can only view affected libs can't build them, have to use run-many as work around and hard to communicate within a large team
Any other relevant information that will help us help you.
I have created a small snippet to able the workspace to run affected:libs:build successfully re-using
@nrwl/workspace
librarieslink to gist --> affected-libs.ts
The text was updated successfully, but these errors were encountered: