Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

no-unresolved and no-missing-require rules report an error with [email protected] #2883

Closed
ddolcimascolo opened this issue Sep 25, 2023 · 1 comment

Comments

@ddolcimascolo
Copy link

ddolcimascolo commented Sep 25, 2023

Hello,

Cross-post from isaacs/node-glob#557

I'm not sure which of the two libraries is responsible for this error, but node is happy to require('glob'), but eslint-plugin-import reports no-unresolved and no-missing-require violations...

Environment

Anything I can do to help ?

Thanks,
David

@ddolcimascolo ddolcimascolo changed the title no-unresolved rule reports an error with [email protected] no-unresolved and no-missing-require rules report an error with [email protected] Sep 25, 2023
@ljharb
Copy link
Member

ljharb commented Sep 25, 2023

isaacs/node-glob#557 (comment)

Looks like isaacs/node-glob@v10.3.6...v10.3.7 switched to building with tshy, but since v10.3.6 has "main", and v10.3.7 does not have "main", that's potentially a breaking change in a patch version.

An argument can be made that since engines.node is >=16 || 14 >=14.17, and all of those versions understand "exports" and don't need "main", that it's not breaking, but eslint-plugin-import doesn't yet understand "exports" (since resolve doesn't yet understand it), so that's what's causing the issue here.

For this plugin, that makes this a duplicate of #2703.

@ljharb ljharb closed this as not planned Won't fix, can't repro, duplicate, stale Sep 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants