Microsoft/vscode

typescript.tsdk not resolved correctly when it starts with the same name as the parent directory

Open

#272761 opened on Oct 22, 2025

View on GitHub
 (1 comment) (0 reactions) (1 assignee)TypeScript (74,848 stars) (10,221 forks)batch import
bughelp wantedtypescript

Description

Does this issue occur when all extensions are disabled?: No

  • VS Code Version: 1.105.1
  • OS Version: Windows 11

Steps to Reproduce:

  1. Create a directory called x and open it in VS Code
  2. Create a .vscode/settings.json with "typescript.tsdk": "x/.yarn/sdks/typescript/lib"
  3. Press ctrl+shift+p, choose "Select TypeScript Version", then Pick "Use Workspace Version"
  4. Note that the error message says

The path c:\path\to\x.yarn\sdks\typescript\lib\tsserver.js doesn't point to a valid tsserver install. Falling back to bundled TypeScript version.

when it should should be c:\path\to\x\x\.yarn\sdks\typescript\lib\tsserver.js

It's because of https://github.com/microsoft/vscode/blob/81a9252210bc64a201449a75995c708aa7a5db96/extensions/typescript-language-features/src/utils/relativePathResolver.ts#L11-L15

Originally introduced in https://github.com/microsoft/vscode/commit/733e208be4cfa85e5a1b2e2ea415843f0a9a7b6d

Workaround: "typescript.tsdk": ".//x/.yarn/sdks/typescript/lib", note the double slash at the start.

I could submit a PR that deletes that code to solve it, but I don't understand what it's there for in the first place.

CC @mjbvz

Contributor guide

Tech stack
typescript
Domain
developer experiencetooling
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic TypeScriptVS Code extension development basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
Examine the file `extensions/typescript language features/src/utils/relativePathResolver.ts` lines 11-15 to understand the path resolution logic. Review the commit history at 733e208be4cfa85e5a1b2e2ea415843f0a9a7b6d to see why the `path.dirname` call was originally added. Consider whether the fix is to remove that line or adjust it to handle cases where the directory name matches the parent directory name. Test with the provided steps and verify that the TypeScript version selection works correctly without altering other path resolutions.