-
-
Notifications
You must be signed in to change notification settings - Fork 95
Doesn't work with global ESLint config #266
Comments
ESLint config resolution is supposed to be handled by I think it's possible ESLint is picking up a config while crawling in the directory tree. |
process.env.LOG_LEVEL='debug'
// or for more detailed traces
process.env.LOG_LEVEL='trace' Then execute a format with ESLint integration enabled. PS: I can't reproduce the issue. It can find my fallback config in my user dir. |
I'm trying to use a global prettier-eslint. It seems like it's not detecting that, whereas linter-eslint does have options for global eslint configs. That would explain why enabling both "Fix on Save"s worked, but isn't ideal. Good solution: be able to specify global prettier-eslint and global eslint config, e.g. linter-eslint's settings page. Not sure if it'd be better to step up tree or just allow people to specify a global prettier-eslint install and/or eslint config. Seems like specifying would leave less room for bugs and might be why the linter-eslint team went that route. |
The strange thing is that, it should be stepping up the tree as-is? |
|
If this helps at all, I'm having the same problem with prettier-eslint finding the file in the project path (one level higher than the package.json). Everything was has been working fine for months until I just noticed the change in formatting using
prettier-atom 0.51.0 |
This seems to be because prettier is looking for the eslint module which has been deprecated and can't now be installed, instead of the linter-eslint module. I can't figure out how to get prettier to look for the correct module though |
linter-eslint has a global option for falling back to
~/.eslintrc
config if no configs are found locally.Your README says prettier-atom looks up system tree for configs, but it doesn't seem to be working.
Here's my prettier-atom config:
It'd be nice if you could config to work with global .editorconfig as well.
The text was updated successfully, but these errors were encountered: