We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
it's a node.js issue: nodejs/node#9435
node.js
the problem occurs when the NODE_OPTIONS environment variable is set and includes --inspect or --inspect-brk and the node app spawns a child process.
NODE_OPTIONS
--inspect
--inspect-brk
parcel spawns child processes which inherit the environment variables. as a result when running e.g.
parcel
NODE_OPTIONS=--inspect hlx up
the console will be flooded with Starting inspector on 127.0.0.1:9229 failed: address already in use messages.
Starting inspector on 127.0.0.1:9229 failed: address already in use
The text was updated successfully, but these errors were encountered:
#189 strip debugger options from NODE_OPTIONS
892f3ff
fixed in 892f3ff
Sorry, something went wrong.
No branches or pull requests
it's a
node.js
issue: nodejs/node#9435the problem occurs when the
NODE_OPTIONS
environment variable is set and includes--inspect
or--inspect-brk
and the node app spawns a child process.parcel
spawns child processes which inherit the environment variables. as a result when running e.g.the console will be flooded with
Starting inspector on 127.0.0.1:9229 failed: address already in use
messages.
The text was updated successfully, but these errors were encountered: