Skip to content
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

enableProjectDiagnostics problem #168410

Closed
thealjey opened this issue Dec 8, 2022 · 1 comment
Closed

enableProjectDiagnostics problem #168410

thealjey opened this issue Dec 8, 2022 · 1 comment
Assignees
Labels
*out-of-scope Posted issue is not in scope of VS Code

Comments

@thealjey
Copy link

thealjey commented Dec 8, 2022

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

  • VS Code Version: 1.74.0
  • OS Version: macOS 13.0.1

Steps to Reproduce:

  1. enable the "typescript.tsserver.experimental.enableProjectDiagnostics" setting

With the feature enabled typescript is unable to find builtin "node:" (eg "node:path") modules or their corresponding type declarations.
And for the packages installed with npm and shipped with d.ts files it also says that type declarations are not found and suggests installing a "@types/" package.

With the feature turned off everything works just fine.

@mjbvz
Copy link
Collaborator

mjbvz commented Dec 13, 2022

This feature is experimental and is not going to be finalized because of issues like this (and it is also not worth iterating on further because it is a dead end)

The issue tracking its replacement is #13953

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
*out-of-scope Posted issue is not in scope of VS Code
Projects
None yet
Development

No branches or pull requests

3 participants