Bug: some types are imported as any about lexical

[2wheeh]

Hmm the thing was in tsconfig:

"moduleResolution" : "bundler"

It's correctly working on "node", it's probably a bug on tsserver or vscode side.

[2wheeh]

.d.ts file in node_modules seems correct though 🤔 :

[2wheeh]

It seems to happen to other methods with union return types quite randomly..
.getParent() should have had same type as .getPreviousSibling: LexicalNode | null

and .d.ts looks correct here as well...

Is anyone have any clue on this? i checked it happens to other repos running lexical. (I cloned to test 😓)

[2wheeh]

I've found the reason !

with moduleResolution: node, the import statement in a .d.ts file resolves '.' to index.d.ts

// something.d.ts
import { /*...*/ } from '.';

However, with moduleResolution: bunder

this path resolves to Lexical.js, which is configured as the main entry in package.json

So, I guess we need to update '.' to './index' to support correct type inference with moduleResolution: bundler.

Or clarify entry for types on package.json ! this would be simpler and more proper solution