Skip to content
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

Termination of dev task won't kill npm processes #452

Open
alansemenov opened this issue Mar 11, 2024 · 0 comments
Open

Termination of dev task won't kill npm processes #452

alansemenov opened this issue Mar 11, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@alansemenov
Copy link
Member

alansemenov commented Mar 11, 2024

gradle dev task executes npm run watch which, in turn, starts several child processes. If user terminates execution of the dev command, these child processes should be terminated as well but they don't. This results in a port used by Browsersync to remain in use indefinitely.

Apparently this is a known bug in Gradle which hasn't been fixed yet.

We should try to somehow implement termination of these child processes ourselves or try to migrate from Browsersync to something else that is not using ports.

browsersync.mov
@alansemenov alansemenov added the bug Something isn't working label Mar 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant