Possibly incorrect module resolution?

[jasonkuhrt]

In a Vitepress project I am seeing the following behaviour.

Given a code block like:

And given this file system in current working directory:

node_modules/
  bar/
    index.d.ts (contains: export declare const foo: number)
bar/
  index.d.ts (contains: export declare const foo2: number)

Then twoslash attempts to resolve the bar import to from ./bar instead of ./node_modules/bar.

If I rm -rf bar then node_modules/bar is used.

I think it might be an error that an import for bar would pick up ./bar before first looking for node_modules/bar.

When I run this in GitHub Actions, this problem does not happen. I am not sure why yet.

[jasonkuhrt]

It's not just about index either. The same issue happens for e.g. import {...} from 'foo/x. In that case instead of looking at the exports field of node_modules/foo/package.json it will use ./foo/x.ts (.d.ts, .ts, doesn't matter) if such a file exists.