Open spamsch opened 3 years ago
We are using utils.run
https://github.com/netlify/build/blob/master/packages/run-utils/README.md to execute the server command.
I tried it out in https://github.com/cypress-io/netlify-plugin-prebuild-example/pull/54
utils.run
that uses execa v3
. The plugin calls "childProcess.kill` which does kill it https://github.com/sindresorhus/execa#kill-a-processAdvice: instead of using npm run develop
command in netlify.toml file, try running the original command. For example
when using npm run develop
command the NPM process remains + Gatsby
But if we use the direct command, execa
can find it and use it
[plugins.inputs.preBuild]
enable = true
start = 'gatsby develop'
and only the single deep process remains
Of course, it would be nice to resolve it and kill the entire tree of processes. I will look into this in the future, opened a question for Netlify team https://github.com/netlify/build/issues/2371
Versions
Describe the bug Process are not stopped
Logs and screenshots
When using the following configuration the processes are not stopped
then processes are not stopped