{"action":"created","issue":{"url":"https://api.github.com/repos/benmosher/eslint-plugin-import/issues/130","labels_url":"https://api.github.com/repos/benmosher/eslint-plugin-import/issues/130/labels{/name}","comments_url":"https://api.github.com/repos/benmosher/eslint-plugin-import/issues/130/comments","events_url":"https://api.github.com/repos/benmosher/eslint-plugin-import/issues/130/events","html_url":"https://github.com/benmosher/eslint-plugin-import/issues/130","id":119360143,"number":130,"title":"Possible readme error for eslint-import-resolver-node","user":{"login":"msikma","id":1507745,"avatar_url":"https://avatars.githubusercontent.com/u/1507745?v=3","gravatar_id":"","url":"https://api.github.com/users/msikma","html_url":"https://github.com/msikma","followers_url":"https://api.github.com/users/msikma/followers","following_url":"https://api.github.com/users/msikma/following{/other_user}","gists_url":"https://api.github.com/users/msikma/gists{/gist_id}","starred_url":"https://api.github.com/users/msikma/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/msikma/subscriptions","organizations_url":"https://api.github.com/users/msikma/orgs","repos_url":"https://api.github.com/users/msikma/repos","events_url":"https://api.github.com/users/msikma/events{/privacy}","received_events_url":"https://api.github.com/users/msikma/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-11-29T13:23:32Z","updated_at":"2015-12-07T12:45:45Z","closed_at":"2015-11-29T14:35:48Z","body":"Hi there. I'm currently attempting to get this plugin working with (the equivalent of) a custom NODE_PATH. Was looking at the [eslint-import-resolver-node](https://www.npmjs.com/package/eslint-import-resolver-node) documentation, which says to add an `import/resolver` key to the `.eslintrc` file, but after checking the code I see that it actually looks for `import/resolve` (in `lib/core/resolve.js`).\r\n\r\nI'm not sure if I'm missing something, or if there's a discrepancy.\r\n\r\nRelevant versions:\r\n\r\n* eslint@1.8.0\r\n* eslint-plugin-import@0.8.1\r\n* eslint-import-resolver-node@0.1.0"},"comment":{"url":"https://api.github.com/repos/benmosher/eslint-plugin-import/issues/comments/162515582","html_url":"https://github.com/benmosher/eslint-plugin-import/issues/130#issuecomment-162515582","issue_url":"https://api.github.com/repos/benmosher/eslint-plugin-import/issues/130","id":162515582,"user":{"login":"benmosher","id":3709196,"avatar_url":"https://avatars.githubusercontent.com/u/3709196?v=3","gravatar_id":"","url":"https://api.github.com/users/benmosher","html_url":"https://github.com/benmosher","followers_url":"https://api.github.com/users/benmosher/followers","following_url":"https://api.github.com/users/benmosher/following{/other_user}","gists_url":"https://api.github.com/users/benmosher/gists{/gist_id}","starred_url":"https://api.github.com/users/benmosher/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/benmosher/subscriptions","organizations_url":"https://api.github.com/users/benmosher/orgs","repos_url":"https://api.github.com/users/benmosher/repos","events_url":"https://api.github.com/users/benmosher/events{/privacy}","received_events_url":"https://api.github.com/users/benmosher/received_events","type":"User","site_admin":false},"created_at":"2015-12-07T12:45:45Z","updated_at":"2015-12-07T12:45:45Z","body":"@msikma: I was just reading through your ESLint Gitter messages, and got a better understanding of what you were after.\r\n\r\nWould it be simpler to have the Node resolver use `NODE_PATH`, if defined on `process.env`? Would be fairly straightforward.\r\n\r\nI generally bake my `NODE_PATH` into build scripts as an `export NODE_PATH=./whatever` up top. Seems like it would follow that the resolver would pick this up and run with it, vs. having to configure it in again in `.eslintrc`."}}