-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
(from benmosher/eslint-plugin-import) packageDir should be relative to eslint config file not cwd #1546
Comments
It sounds like what should be done is that plugin should be modified so you can set an option for making the director relative to where the configuration file is, or give it an absolute path. I'll leave a comment on that issue. |
I can confirm the issue, but we can specify config in .eslintrc.js and it helps with imports:
|
Maybe we should prefix the eslint commands with |
I'll close this, as the way to get the eslint-plugin-import plugin to work is to create |
I ran into the issue described here, was wondering if you'd consider this a wontfix or not. I ran into this due to
set autochdir
which I'm aware is known to cause breakage. Thanks!Information
VIM version
VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Apr 25 2018 22:19:32)
macOS version
Operating System: macOS
:ALEInfo
What went wrong
As per the original issue:
packageDir
is resolved relative to cwd instead of wherever the eslint config is.Reproducing the bug
eslint-plugin-import
plugin, open some file in a different dir than.eslintrc
or wherever the config is; see that imports are resolved correctlyset autochdir
, etc.)The text was updated successfully, but these errors were encountered: