![import/no-import-module-exports is triggered on all imports when a variable named module is used. · Issue #2297 · import-js/eslint-plugin-import · GitHub import/no-import-module-exports is triggered on all imports when a variable named module is used. · Issue #2297 · import-js/eslint-plugin-import · GitHub](https://user-images.githubusercontent.com/33164598/140975641-ae321fa2-45ff-4cec-a688-061ac1ea7bb0.png)
import/no-import-module-exports is triggered on all imports when a variable named module is used. · Issue #2297 · import-js/eslint-plugin-import · GitHub
![Getting "No default export found in module import/default" running eslint · Issue #507 · react-native-share/react-native-share · GitHub Getting "No default export found in module import/default" running eslint · Issue #507 · react-native-share/react-native-share · GitHub](https://user-images.githubusercontent.com/517228/58434578-c75f4180-8092-11e9-934e-29767bba64a7.png)
Getting "No default export found in module import/default" running eslint · Issue #507 · react-native-share/react-native-share · GitHub
![Node.js now supports named imports from CommonJS modules, but what does that mean? - Simon Plenderleith Node.js now supports named imports from CommonJS modules, but what does that mean? - Simon Plenderleith](https://simonplend.com/wp-content/uploads/2020/09/tweet-screenshot.png)
Node.js now supports named imports from CommonJS modules, but what does that mean? - Simon Plenderleith
![Feature Request: Make ES module exports conform to an interface using triple slash directive · Issue #32423 · microsoft/TypeScript · GitHub Feature Request: Make ES module exports conform to an interface using triple slash directive · Issue #32423 · microsoft/TypeScript · GitHub](https://user-images.githubusercontent.com/3070389/61316553-887f7980-a801-11e9-8c3c-9ce6d7522b9d.png)