import/no-unresolved with webpack modules/aliases in the VS Code

Update:

So, there are few separate issues.

1. To fix issue now, I can adjust my config: replace object spreading with Object.assign, or use babel-register.
2. Something interpret Unexpected token ... as ESLint error and show no-undesolved, no-duplicate and other. Which is wrong - it should be SyntaxError in ESLint output. It happens because node v7.9.0 in VS Code can’t launch webpack config with object spread syntax.
3. May be vscode-eslint can launch .eslintrc.js and webpack config with local node, not with bundles one?

---

Original text

Faced with such issue. There is no errors while launching eslint from terminal.

Trying to reproduce error in clean repository, but without success yet.

[alecf]

This was driving me bonkers and I was getting other odd errors from the import plugin. Just for kicks I put:

require('babel-register')

at the top of my .eslintrc and magically everything seems to work now! (I was already using babel-register elsewhere in my project, so it was already installed)

It seems like vscode-eslint runs eslint as a library, and JS imports aren’t recognized without babel-register

[viT-1]

I changed webpack config from this: resolve: { alias: { '~': path.resolve(__dirname), '@': path.resolve(__dirname, './src'), }, }, to this: resolve: { alias: { '~': path.resolve(__dirname), '@': path.resolve(__dirname, 'src'), }, },

It seems to be ok. But intellisence not showing fresh added methods in imported file, but show arguments intellisence after I writing the name of “fresh” method completely.