microsoft / microsoft/vscode-edge-devtools

Edge Tools for VS Code in Windows cannot resolve extends in tsconfig.json

Open
#962 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug tracked
Dominant language
TypeScript
Stars
827
Forks
358
Avg merge
20h 32m
Merged PRs (30d)
10

Description

Environment (please complete the following information):

Version: 1.66.0 (user setup)
Commit: e18005f0f1b33c29e81d732535d8c0e47cafb0b5
Date: 2022-03-30T05:50:14.623Z
Electron: 17.2.0
Chromium: 98.0.4758.109
Node.js: 16.13.0
V8: 9.8.177.11-electron.0
OS: Windows_NT x64 10.0.22581

Edge Tools: v1.4.6

VS Code is running on Windows without WSL.

Describe the bug:

Edge Tools reported an error that it cannot find the target file in extends field of tsconfig.json. It seems that it cannot resolve the node_modules directory properly.

image

The error is gone if Microsoft Edge Tools extension is disabled.

image

Repro steps:

  1. Clone this repository: https://github.com/tkesgar/vscode-tsconfig-extends-error-example
  2. Open in VS Code with extension enabled
  3. View tsconfig.json

Expected behavior:

No error is reported, since it is the recommended practice from https://github.com/tsconfig/bases#available-tsconfigs.

Additional context:

The error does not appear if I open VS Code in WSL.

image

Workaround:

  • Run VS Code under WSL in Windows
  • Disable the plugin

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Clone tkesgar/vscode-tsconfig-extends-error-example, open it in VS Code on Windows with Edge Tools v1.4.6 enabled, and inspect tsconfig.json while comparing behavior with the extension disabled or under WSL. Trace how the extension resolves the tsconfig.json extends target and verify that the recommended node_modules-based configuration no longer reports an error on Windows.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vscode
Domain
developer-experience, devtools
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.