Support variables when resolving values in settings
Hi, I was just reading the [latest updates](https://code.visualstudio.com/updates) and it says one can install `typescript@next` globally and then set `typescript.tsdk` so VS Code can use the appropriate version/installation. In a team environment, I'd like to put that setting in our project, something like: `.vscode/settings.json`: ``` json { "typescript.tsdk": "%APPDATA%/npm/node_modules/typescript/lib" } ``` The problem is restarting VS Code results in an error: ``` The path c:\Projects\Derp\%APPDATA%\npm\node_modules\typescript\lib doesn't point to a valid tsserver install. TypeScript language features will be disabled. ``` Now the setting needs to be per-person because I highly doubt my teammates have `tsc` installed in `C:\Users\Olson\AppData\Roaming\npm\node_modules\typescript\lib` :wink: Could we get environment variables evaluated on that and all other settings that involve paths? I haven't tested other paths, but I see these in the Default Settings: - `git.path` - `markdown.styles` - `json.schemas` - `typescript.tsdk` - `php.validate.executablePath`
Posted by OlsonDev on Feb 9, 2016, 1:18 AM
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.5,000 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 variables when resolving values in settings
Hi, I was just reading the [latest updates](https://code.visualstudio.com/updates) and it says one can install `typescript@next` globally and then set `typescript.tsdk` so VS Code can use the appropriate version/installation. In a team environment, I'd like to put that setting in our project, something like: `.vscode/settings.json`: ``` json { "typescript.tsdk": "%APPDATA%/npm/node_modules/typescript/lib" } ``` The problem is restarting VS Code results in an error: ``` The path c:\Projects\Derp\%APPDATA%\npm\node_modules\typescript\lib doesn't point to a valid tsserver install. TypeScript language features will be disabled. ``` Now the setting needs to be per-person because I highly doubt my teammates have `tsc` installed in `C:\Users\Olson\AppData\Roaming\npm\node_modules\typescript\lib` :wink: Could we get environment variables evaluated on that and all other settings that involve paths? I haven't tested other paths, but I see these in the Default Settings: - `git.path` - `markdown.styles` - `json.schemas` - `typescript.tsdk` - `php.validate.executablePath`
Comments (0)
No comments yet. Start the discussion.