utils: [Fix] report the error stack on a resolution error

[sompylasar]

Resolve errors are most likely caused by invalid configuration, and the reason is easier to determine with the full details rather than just err.message.

See #536

With this change, it reports something like:

import/no-unresolved: Resolve error: SyntaxError: Unexpected token import
    at exports.runInThisContext (vm.js:53:16)
    at Module._compile (module.js:387:25)
    at Object.Module._extensions..js (module.js:422:10)
    at Module.load (module.js:357:32)
    at Function.Module._load (module.js:314:12)
    at Module.require (module.js:367:17)
    at require (internal/module.js:16:19)
    at module.exports (/__censored__/webpack/configFactory.js:216:3)
    at configProdClient (/__censored__/webpack/configProdClient.js:5:36)
    at Object.<anonymous> (/__censored__/webpack/configForEslintImportResolver.js:1:126)

[benmosher]

Ah, cool. Makes sense, though in retrospect I'm thinking maybe the stacktrace should be emitted by a debug logger instead of the error message, since it's so verbose.

What do you think?

[sompylasar]

I think the stack for this specific error is meaningful at the exact place where the error has occurred, to be able to quickly fix the error without switching context.

I use Atom Linter, so I expect all the error details in the linter error message which editor shows me.

We could also log the error, but the core benefit is being able to see its cause quickly.

[ghost]

Is this PR moving? It would really be helpful.

[sompylasar]

@st-sloth Looks like the tests need to be updated to reflect the change. I'll have a look if time allows.

[sompylasar]

Changed the logic slightly to only add stack to unknown errors (that do not originate from eslint-plugin-import itself, which is designated by the error name of 'EslintPluginImportResolveError'). Updated the tests to reflect the change.

[coveralls]

Coverage increased (+0.03%) to 96.343% when pulling aed7a73 on sompylasar:patch-1 into b511da2 on benmosher:master.

[coveralls]

Coverage remained the same at 97.356% when pulling 931363f on sompylasar:patch-1 into db471a8 on benmosher:master.

[coveralls]

Coverage remained the same at 97.356% when pulling 931363f on sompylasar:patch-1 into db471a8 on benmosher:master.