You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it is starting to be good practice to alway specify the extension of a file, i.e. "import/extensions": ["error", "always"] as this will be required with browsers' module loaders.
However, this causes issues when using with webpack or others and importing libraries installed in the node_modules (e.g. import 'react') that cannot have the '.js' extension.
It would be useful to be able to create a case for global imports, e.g. [<enabled>, "alway", { "globals": "never" }].
The text was updated successfully, but these errors were encountered:
Enhancement proposal: global case for extensions.
I think it is starting to be good practice to alway specify the extension of a file, i.e.
"import/extensions": ["error", "always"]
as this will be required with browsers' module loaders.However, this causes issues when using with webpack or others and importing libraries installed in the
node_modules
(e.g.import 'react'
) that cannot have the'.js'
extension.It would be useful to be able to create a case for global imports, e.g.
[<enabled>, "alway", { "globals": "never" }]
.The text was updated successfully, but these errors were encountered: