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
vscode-jest version
node -v
npm -v
yarn --version
npm ls jest
npm ls react-scripts
[email protected] ├─┬ ..../[email protected] │ └─┬ [email protected] │ └── [email protected] deduped ├─┬ [email protected] -> ./ │ └── [email protected] deduped ├── [email protected] └─┬ [email protected] └── [email protected] deduped
npm run test
node_modules/.bin/jest
"jest.nodeEnv": { "MYENV": "TRUE" }
When running the test without debugging, it works and the env variable is set in the process. But when using the debugging, the env variable is empty.
The text was updated successfully, but these errors were encountered:
That's true and I agree we should take care of this. Meanwhile, you can fix it with a custom debug config.
Sorry, something went wrong.
Hey everyone,
The fix is out! Check out the pre-release v6.3.0-next and let us know if you run into any issues.
Successfully merging a pull request may close this issue.
Environment
vscode-jest version
: v6.1.1node -v
: v20.10.0npm -v
oryarn --version
: 10.2.3npm ls jest
ornpm ls react-scripts
(if you haven’t ejected):Prerequisite
npm run test
ornode_modules/.bin/jest
) npx jestSteps to Reproduce
"jest.nodeEnv": {
"MYENV": "TRUE"
}
When running the test without debugging, it works and the env variable is set in the process.
But when using the debugging, the env variable is empty.
The text was updated successfully, but these errors were encountered: