Open sebbi08 opened 5 months ago
vscode-jest version
node -v
npm -v
yarn --version
npm ls jest
npm ls react-scripts
...@3.7.0 ├─┬ ..../eslint-config-ts@1.6.6 │ └─┬ eslint-plugin-jest@27.6.0 │ └── jest@29.7.0 deduped ├─┬ ...@3.7.0 -> ./ │ └── jest@29.7.0 deduped ├── jest@29.7.0 └─┬ ts-jest@29.1.1 └── jest@29.7.0 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.
That's true and I agree we should take care of this. Meanwhile, you can fix it with a custom debug config.
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.