Support envfile for tasks.json
The node and Go debuggers both support specifying an env file for environment variables instead of the `env` hash. It would be great if we could use the same file in tasks.json to have a single source of truth that can also be used by non-vscode scripts
Posted by felixfbecker on Oct 23, 2017, 6:47 PM
Tags
Related issues
- some bike vendor told me that the biggest problem with regular to ebike conversion was that regular bike frames were not strong enough to...
- I think of this as the kiosk economy.
- What a goofy comment.
- There's lots of evidence for positive influences of Caffeine on the body (some negative as well), especially the brain.
- Compose support in WSLc
- [RFC] Roadmap to v2.0
Raise real-world problems, find people facing the same issue, and discuss solutions.4,500 issues0 comments
support (Other)
some bike vendor told me that the biggest problem with regular to ebike conversion was that regular bike frames were not strong enough to...
I think of this as the kiosk economy.
What a goofy comment.
There's lots of evidence for positive influences of Caffeine on the body (some negative as well), especially the brain.
Compose support in WSLc
[RFC] Roadmap to v2.0
[Feature]: Add TurboQuant Support for KV Cache Quantization
Support for AGENTS.md and .agents/skills/, the community has been asking since August 2025
Support envfile for tasks.json
The node and Go debuggers both support specifying an env file for environment variables instead of the `env` hash. It would be great if we could use the same file in tasks.json to have a single source of truth that can also be used by non-vscode scripts
Comments (0)
No comments yet. Start the discussion.