-
Notifications
You must be signed in to change notification settings - Fork 0
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
Propose rule disabling #5
Conversation
marking our aliases with import-js/eslint-plugin-import#89 (comment) (i was actually just looking into this issue yesterday and this plugin seems promising) |
@gettinToasty something like this? ["module-resolver", {
"root": ["."],
"cwd": "babelrc",
"extensions": [".js", ".jsx"],
"alias": {
"@commercial": "./app/assets/javascripts/client",
"@shared": "./app/assets/javascripts/shared"
}
}] |
specifically talking about this:
|
Closing since we are moving towards removing |
@gettinToasty oh sorry, wrong repo lol! |
@ThisIsErik lol |
Are there any extensions of eslint that would be able to take webpack configuration into account for resolving imports? |
@berfarah thats literally what i just linked to above lol |
My bad, I missed it |
On Commercial, we have a lot of imports that following this format:
and
eslint
flags these lines as:Unable to resolve path to module '@commercial/constants/ui'
'@commercial/constants' should be listed in the project's dependencies.
Missing file extension for "@commercial/constants/ui
I propose that we disable these three rules as we don't use file extensions in our imports and because the
@commercial/blah
pattern is very common and used everywhere in the code base.Suggestions, feedback and alternatives welcome!