The option --target should be available for both :libs and :apps

[dianjuar]

Please make sure you have read the submission guidelines before posting an issue

Expected Behavior

The parameter --target is not present on affected:libs or affected:apps. It exists for all the stuff in your workspace nx affected --target=deploy but is going "deploy" my apps and libraries and if I want only deploy my libraries and I can't do that.

The option --target should available for both :libs and :apps

Current Behavior

When I run nx affected:libs --target=deploy or nx affected:apps --target=deploy

And nothing more happens. Should run the deploy architect of my libraries or apps

Steps to Reproduce

For projects

1. run nx affected:apps --target=deploy

For libraries

1. Have a library in your workspace
2. run nx affected:libs --target=deploy

Context

• version of Nx used
  • 8.5.0

Other

I'm trying to use a new feature of the Angular CLI, ng deploy to only deploy the libraries with ngx-deploy-npm

[FrozenPandaz]

This makes sense.

This should apply to configuration as well. And when those options are not passed, the full list should be printed.

Alternatively, you should be able to use print-affected for this as well.

Would somebody be interested in contributing this feature?

[ashbrener]

I am having the same issue. I need to use the deploy target to publish libs to npm.

[dianjuar]

Would somebody be interested in contributing this feature?

I would love to do so 😃

[dianjuar]

Any recommendations for my adventure besides the CONTRIBUTING.md guidelines and How to contribute to Nx Video @FrozenPandaz ?

[FrozenPandaz]

Sorry, I thought you were only expecting those projects to be printed when I first read the issue.

In regards to being able to "deploy" libs and apps separately, I think it makes more sense to give them different target names.

The way I see it, apps get deployed to a hosting service while libs more specifically get published to a registry. Thus, I would call the target "publish". You might not be able to use ng deploy as you want... but you can use nx publish because we accept any target name. You can also use the more verbose ng run proj-name:publish or nx run proj-name:publish. Having separate target names means that you can use nx affected --target publish to publish affected projects to npm and nx affected --target deploy to deploy affected projects to a hosting service.

Sorry for the confusion.

[github-actions]

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.
If we missed this issue please reply to keep it active.
Thanks for being a part of the Nx community! 🙏