ESlint errors from import/no-unresolved

[cpojer]

Describe the bug

Somehow pnpm v9 and eslint with the import/no-unresolved plugin don't play well with TinyBase's structure. It yells at me because it can't resolve some module with its resolver.

Your Example Website or App

https://github.com/cpojer/pnpm-eslint-tinybase-bug

Steps to Reproduce the Bug or Issue

• Ensure you are on pnpm v9.
• Clone https://github.com/cpojer/pnpm-eslint-tinybase-bug
• Run pnpm install and pnpm eslint .

It will show that it cannot resolve the paths.

Expected behavior

eslint should be happy with the custom paths.

Screenshots or Videos

No response

Platform

No response

Additional context

No response

[jamesgpearce]

Thanks for making it easy to repro! :)

[jamesgpearce]

So just to be clear, it seems to work fine with NPM and I'm wondering why PNPM puts things in a different place. Let me dig a bit more.

[jamesgpearce]

Wait what, no it doesn't. Repros in NPM too. The problem is no-unresolved not apparently understanding the export rules in package.json or something like that.

[cpojer]

Ah, should we file this against the eslint import plugin instead then?

[jamesgpearce]

https://github.com/import-js/eslint-plugin-import/issues/1810

[jamesgpearce]

It seems possible to maybe just touch empty files to keep the linter happy but that is such a hack. Until this is solved on the resolver side, it seems the best thing to do is document this issue in the Imports guide.

[jamesgpearce]

Documented in #7286a123f007ca9cd3953421d78093472a11c140 but I'll leave this open on the off-chance they fix it. exports should be pretty mainstream by now!

[jamesgpearce]

I'm hoping we are past these sorts of issues in v5.0.0-beta.21

If you get a chance could you give it a whirl please? Thanks!

[cpojer]

Yup, seems to work. Very nice, thank you.