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
--inspect
--inspect-brk
Originally posted by Guid75 September 2, 2023
Hi, Wondering why vitest does not allow to pass host and port to --inspect and --inspect-brk flags like nodejs does. My process is running on a docker container and I need to pass "0.0.0.0" instead to "127.0.0.1" in order to access it from my debugger.
Hi,
Wondering why vitest does not allow to pass host and port to --inspect and --inspect-brk flags like nodejs does.
My process is running on a docker container and I need to pass "0.0.0.0" instead to "127.0.0.1" in order to access it from my debugger.
Let's add support for passing URL and port to Vitest's --inspect flags. Similar as in https://nodejs.org/en/learn/getting-started/debugging#command-line-options. This considers both --inspect and --inspect-brk flags.
--inspect=127.0.0.1:9229
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Discussed in #4062
Originally posted by Guid75 September 2, 2023
Let's add support for passing URL and port to Vitest's
--inspect
flags. Similar as in https://nodejs.org/en/learn/getting-started/debugging#command-line-options. This considers both--inspect
and--inspect-brk
flags.--inspect
-> enabled and uses the default host and port that Node chooses--inspect=127.0.0.1:9229
-> enabled and uses the defind host and portThe text was updated successfully, but these errors were encountered: