[BUG] @nx-dotnet/core:serve produces invalid executing command

[epic-media]

Versions 1.3.0 and 1.3.1 produce the following executing command for @nx-dotnet/core:serve (which exits immediately with Exit Handler Called):

dotnet watch --project D:\path\to\project.csproj run --configuration Debug --runtime win-x64

When rolling back to 1.2.0 the correct command is generated and executes ok:

dotnet watch run --project D:\path\to\project.csproj --configuration Debug --runtime win-x64

[AgentEnder]

Hey, I'll look into this sometime today. In 1.2 and earlier nx-dotnet used a custom filewatcher instead of dotnet watch, this was changed in 49ce6bc.

Does the test executor work fine for you?

[AgentEnder]

Never mind, this was an easy fix. I abstracted the child_process logic out into a utility and didn't setup the promise correctly. This should be fixed in an hour or so after all the pipelines finish.

[github-actions]

🎉 This issue has been resolved in version 1.3.2 🎉

The release is available on:

• v1.3.2
• GitHub release

Your semantic-release bot 📦🚀

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.