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
If I use your conf from README and also do (FYI I'm using airbnb eslint conf):
"import/extensions": [ "error", "ignorePackages", { "js": "always", "cjs": "always", "jsx": "always", "ts": "never", "tsx": "never", "json": "always" } ]
then eslint doesn't complain if I import a ts/tsx file without an extension, e.g.:
import Root from 'components/Root'; // no errors for this tsx file
If I change import/extensions conf and say "tsx": "always" instead, then I get:
import/extensions
"tsx": "always"
Missing file extension "tsx" for "components/Root" eslint[import/extensions]
When I import it as a js file there are no errors and that's great:
js
import Root from 'components/Root.js'; // great, but I need the error when the .js extension is missing
So how come your extension isn't jumping out of joy to step in and save the day :)
Thanks
The text was updated successfully, but these errors were encountered:
Closing. I've just realized it happens only when import uses a webpack alias, so this is a dupe of: #10
Sorry, something went wrong.
No branches or pull requests
If I use your conf from README and also do (FYI I'm using airbnb eslint conf):
then eslint doesn't complain if I import a ts/tsx file without an extension, e.g.:
If I change
import/extensions
conf and say"tsx": "always"
instead, then I get:When I import it as a
js
file there are no errors and that's great:So how come your extension isn't jumping out of joy to step in and save the day :)
Thanks
The text was updated successfully, but these errors were encountered: