resolve paths in eslint config

[ForbesLindesay]

Paths to plugins in eslint should be fully resolved in the same way they are in babel's config.

See comment: #149 (comment)

Without this, editor plugins will fail to find the local eslint config.

[gaearon]

Thanks for explaining. Would you like to make a PR?

[ForbesLindesay]

Happy for someone else to fix if they get there first :)

[gaearon]

I looked at this, and it is just not possible right now: eslint/eslint#3458. However there seems to be discussion on implementing it so it‘s not too bad.

This is only a problem with npm 2 (and in very rare cases with npm 3 but we shouldn’t hit those cases). So I think we can punt on this for now.

Longer term, I think something like #215 would be the right solution, but it requires buy-in from the tool vendors.

[ForbesLindesay]

It works fine. I do it in https://github.com/ForbesLindesay/eslint-config-forbeslindesay/blob/master/index.js and have been using this extensively without issue.

[ForbesLindesay]

OK, doesn't work with "plugins" apparently, only parser.

[gaearon]

Yeah. 😢

[ForbesLindesay]

I would attempt to help fixing this, but I don't want to repeat my past experiences of attempting to contribute to eslint.