-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
import/no-import-module-exports is triggered on all imports when a variable named module is used. #2297
Comments
This updates eslint and airbnb eslint. I also upgraded husky cause why not. Resolved some new issues caused by airbnb upgrade. Disabled a broken rule. See import-js/eslint-plugin-import#2297 closes #99 closes #100
This updates eslint and airbnb eslint. I also upgraded husky cause why not. Resolved some new issues caused by airbnb upgrade. Disabled a broken rule. See import-js/eslint-plugin-import#2297 closes #99 closes #100
Specifically, it's two things that are triggering the false positive - the presence of at least one I'm looking into if there's an easy way to confirm whether |
Oh, that's the issue. Yeah, I guess that is kinda my fault then. Not entirely sure the best way to handle this but thanks for taking a look at it. |
Hello there. I've been updating dependancies and now in all files I import fs/promises in I am getting
Cannot use import declarations in modules that export using CommonJS (module.exports = 'foo' or exports.bar = 'hi') import/no-import-module-exports
I'm not entirely sure whats happening here.
Here is some info:
.eslintrc.json
Eslint version
^8.2.0
Eslint plug import version
^2.25.2
An example file that is getting the error:
A screenshot of the error happening
A related issue from eslint-config-airbnb-base
airbnb/javascript#2496
The text was updated successfully, but these errors were encountered: