VS Code Extension/LSP and rootDirs
The Deno VS Code extension and LSP don't seem to respect the
compilerOptions.rootDirs setting. I've created a repro here: https://github.com/andymccurdy/deno-rootdirs
The default TypeScript VS Code extension and LSP respect this setting and they can see imports from other rootDirs.GitHub
GitHub - andymccurdy/deno-rootdirs: Repro showing error in Deno's V...
Repro showing error in Deno's VS Code extension or LSP - andymccurdy/deno-rootdirs
2 Replies
I got the LSP/VS Code extension working by changing the import statement to:
import type { Foo } from './$types.d.ts'. Didn't realize that import { Foo } would behave differently from import type { Foo }. Adding the .d.ts extension also makes sense since I'm not using --unstable-sloppy-importsAny progress yet dude? @Sedrik