Dev Scripts: Leftover Node.js Processes After Removing Nuxt #5630
Labels
kind/bug
Something isn't working
kind/quality
quality improvements, refactoring, Automation via CI, E2E, Integration, CLI or REST API
Milestone
After removing Nuxt from Rancher Desktop, we are encountering an issue where multiple Node.js processes are left after exiting a development build. This behavior is related to Vue CLI spawning child processes that are not properly tracked and terminated by the development script.
Expected Behavior
When running a development build, we expect all Node.js processes to be cleanly terminated once the build is completed.
Steps to Reproduce
pslist | select-string "node"
Actual Behavior:
After running a development build, we observe that multiple Node.js processes are still active.
The text was updated successfully, but these errors were encountered: