You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using the following versions:
nx: 16.2.1
nx-dotnet: 1.22.0
My solution contains a set of c# microservice projects defined as nx apps and a few shared class libraries which are directly referenced by those microservice projects.
The microservice projects were scaffolded using the @nx-dotnet/core:application generator (main point here is they have a serve target using the @nx-dotnet/core:serve executor), and the libraries were scaffolded using the @nx-dotnet/core:library generator - these have the default build and lint targets.
the microservice apps get started correctly with the dotnet watch command, but in addition to that nx also tries to start the class library projects using dotnet watch and this errors out as expected.
The question here is: why is nx trying to start the class library projects at all when those don't have the serve target defined, and why is it trying to do that with the @nx-dotnet/core:serve executor - is this behavior intended?
I've currently solved this using the run-many --exclude flag so that the shared class library projects are excluded from the run, but the default behavior seems like a bug, just not sure if this is a problem in @nx-dotnet or nx itself.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm using the following versions:
nx: 16.2.1
nx-dotnet: 1.22.0
My solution contains a set of c# microservice projects defined as nx apps and a few shared class libraries which are directly referenced by those microservice projects.
The microservice projects were scaffolded using the @nx-dotnet/core:application generator (main point here is they have a serve target using the @nx-dotnet/core:serve executor), and the libraries were scaffolded using the @nx-dotnet/core:library generator - these have the default build and lint targets.
When I run the following command:
the microservice apps get started correctly with the dotnet watch command, but in addition to that nx also tries to start the class library projects using dotnet watch and this errors out as expected.
The question here is: why is nx trying to start the class library projects at all when those don't have the serve target defined, and why is it trying to do that with the @nx-dotnet/core:serve executor - is this behavior intended?
I've currently solved this using the run-many --exclude flag so that the shared class library projects are excluded from the run, but the default behavior seems like a bug, just not sure if this is a problem in @nx-dotnet or nx itself.
Beta Was this translation helpful? Give feedback.
All reactions