import/named does not report non-existent exports in yarn workspace

[jd2rogers2]

https://github.com/jd2rogers2/eslint-plugin-import-bug-minimal-repo for testing it for yourself

as seen above, no report for import/named despite not having an helloFooV2 export from foo/index.js
foo and bar are both separate workspaces, bar lists foo as a dependency, and foo is in node_modules
i would expect it to report
maybe a larger issue as there is also #1832

[Skidle]

Hey @jd2rogers2 , I encountered a similar false positive error in my project and managed to fix it with the following:

• change exports in foo workspace to ES6 exports (same for imports in bar)
• add 'import/ignore': ['!^@my'], under settings in eslint configuration. You're extending airbnb-base config, which has defined custom import/ignore settings: https://github.com/airbnb/javascript/blob/master/packages/eslint-config-airbnb-base/rules/imports.js#L26. So you need to override those, because yarn workspaces are installed in node_modules (in your case under @my folder.

[jd2rogers2]

@Skidle thanks for taking a look!
i'm not so sure it's because of the airbnb extension though
here i remove the extension and just use the plugin and rule directly, and still eslint . does not report

[Skidle]

@jd2rogers2 yes, since my comment I realized that it happens with or withour airbnb plugin. If you don't use airbnb config, import/ignore will be node_modules by default, effectively ignoring yarn workspaces too.
So you need to add 'import/ignore': ['!^@my'], to ignore anything that's not your workspace.

[jd2rogers2]

@Skidle still no luck on my end :(
i tried out your solution here but i don't get any eslint reports for the import that i expect should receive an error
(even added new rule to make sure eslint command is running correctly)

were you testing in your own repo or by cloning down mine? if you're working in another project would love to be able to find out the differences somehow
and thanks again for you help and time on this!

[Skidle]

@jd2rogers2 you need also to change require to import from in bar.js. Works for me here :)

[andrewzey]

I've just encountered this and was able to determine that the existence of the "import/resolver" key, even if the value is just an empty object, is what's causing import/named to not detect invalid imports.

Still working on figuring out how to get it working with an import/resolver, but that should give some clue.