We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
According to 3.4.1.1.1 File extensions in import paths, "the .js file extension is not optional in import paths and must always be included."
I guess this rule shouldn't be limited to '.js' but to all imported modules. Nevertheless, eslint-config-google should be able to enforce 3.4.1.1.1.
eslint-config-google
Currently, I'm using import/extension from eslint-plugin-import with this config:
import/extension
eslint-plugin-import
rules: { // ... "import/extensions": ["error", "always"], // ... }
In order to enforce 3.4.1.1.1 one-to-one, "import/extensions": ["error", { js: "always" }] is the corresponding configuration.
"import/extensions": ["error", { js: "always" }]
I suggest to include (copy?) import/extension into eslint-config-google.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
According to 3.4.1.1.1 File extensions in import paths, "the .js file extension is not optional in import paths and must always be included."
I guess this rule shouldn't be limited to '.js' but to all imported modules. Nevertheless,
eslint-config-google
should be able to enforce 3.4.1.1.1.Currently, I'm using
import/extension
fromeslint-plugin-import
with this config:In order to enforce 3.4.1.1.1 one-to-one,
"import/extensions": ["error", { js: "always" }]
is the corresponding configuration.I suggest to include (copy?)
import/extension
intoeslint-config-google
.The text was updated successfully, but these errors were encountered: