-
Notifications
You must be signed in to change notification settings - Fork 140
Linting in nested app causes Error: Cannot read config package #422
Comments
Does cd C:\git\project\webroot\private\src
eslint foo.js Also it looks like you are trying to use the built in version of |
sorry, i do have eslint installed at project level as a |
So the reason I thought you didn't have it installed there is because the |
Yea, anything I can do to help resolve this? |
Finally took some time to try to reproduce this, and it looks like |
potentially it could be that it should check it based on the location of the eslintrc file? |
Unfortunately we can't assume that the presence of an |
@IanVS thanks for the input. Unfortunately that is the present setup I already have (i.e. an .eslintignore at the project root). |
@Arcanemagus I think our only real shot here would be to give something like node-which another try. I believe that would solve this particular case, at least. |
If you mean |
any update on this? |
I'm surprised to hear that npm-which doesn't work in this case. @timoxley, can you tell if this is a situation which it should be able to handle correctly? |
I am also seeing this issue. atom linter-eslint cannot find airbnb module. |
If anyone needs a hack to get this working, install the modules needed directly into your atom package. Like this: #259 |
@dijs What is your project's structure that isn't working? Does |
Yes. It does. |
@dijs The first question was just as important 😉. |
Sorry. I don't really understand what you are asking there. linter-eslint errors out because it cannot find the airbnb module I have locally installed. |
Can you explain your structure, similar to #422 (comment) ? |
Oh sure.
|
What version of linter-eslint and Atom are you using? That structure should work perfectly fine... |
Atom: 1.5.3 |
I'd suggest opening a new issue, since this issue is for something entirely different. |
Created #445 |
@Arcanemagus This was true, but should no longer be with the latest
@IanVS Yes, it should! |
Just retested this issue and it seems to have been fixed by an update to |
The structure of my present project is as followed:
So when editing
foo.spec.js
, it goes up the path and picks up the.eslintrc
file, and loadseslint-config-airbnb
(specified in.eslintrc
) at the root levelnode_modules
. However, when editingfoo.js
, it does recognise that it should loadeslint-config-airbnb
, but it attempts to resolve it fromproject/webroot/private/node_modules
and notproject/node_modules
.It gives the following error
The text was updated successfully, but these errors were encountered: