LSP doesn't offer auto-importing packages

[jansedlon]

Extension Version

0.20251203.1

VS Code Version

1.107.0-insider

Operating system Version

MacOS 26.1

Steps to reproduce

1. Create an empty TypeScript project
2. Install typescript-result
3. Create index.ts
4. Type Result and nothing happens

Issue

I noticed somewhere that auto-imports are mostly done, but in my work project, it doesn't auto-import most of the packages that I have installed. It usually auto-imports built-in dependencies such as node:crypto or global types, but not installed deps.

Seems not to be an issue with pnpm, catalog dependencies, etc. It happens with npm as well.

I'm really sorry if this is a current limitation and has been mentioned somewhere, and I didn't notice.

[GeordiD]

I think I'm experiencing the same thing. I seem to get auto-import suggestions when typing for functions inside the codebase, but external packages aren't coming up (i.e. react's useState).

One other thing: quick fix doesn't seem to be identifying that something needs to be imported, or at least the eslint rules complaining about the resulting code not being safe (because there's no useState import) seems to be winning. When I flip back to the non-experimental server the quick fix suggestion correctly identifies that I need to import useState. I'm noticing this also happens for internal imports: while typing an un-imported function that exists in another file I'll get good suggestions, but if I don't pick one and try to use quick-fix it won't suggest that import anymore.

Just trying to throw in more data to this issue. Right now this is happening in my work repo, but if I need to make a reproduction I'm happy to.

Extension version: 0.20251013.2
Cursor Version: 1.7.33 (Universal)
VSCode Version: 1.99.3
Not a monorepo
Using pnpm