-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
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
npm/node run doesn't get env set #26
Comments
It might be that mirrord doesn't even load into it because they use |
Does this only happen on vscode or also with the CLI? |
Only on VS Code - see here. |
Trying to reproduce in https://github.com/t4lz/npm-dotenv - could not reproduce the issue so far. |
@t4lz Thanks for posting the project. The dotenv is external (meaning they use the cli to run their code) |
Ohh, so they're running |
Did that and it still doesn't reproduce for me. Trying to think what I could be doing differently. |
There's a specific launch configuration for npm run script. They used it. |
When running that way (clicking on the little "Debug" button above This of course means the layer is not injected into the process. This is not a SIP issue, it also wouldn't work on Linux. Trying to think how we could support this way of launching. I don't think simply changing the request type would do, because it seems this configuration does not contain the information of which file to run etc. Also probably it's a different flow for the IDE. |
Am I not using it in the commit I linked above? (not talking about the debug button in |
They had something like this: {
"command": "npm run build:prod",
"name": "Run npm start",
"request": "launch",
"type": "node-terminal"
}, |
When running using npm/node the remote env isn't fetched.
The text was updated successfully, but these errors were encountered: