Jacob Mischka

I think the problem is that currently `eslint-import-resolver-babel-module@latest` resolves to `4.0.0-beta.3`, which isn't compatible with `babel-plugin-module-resolver@latest`. It seems like `@beta` for both aren't compatible either unfortunately, but locking them to...

Sorry, this is a private project. I'll try to throw something together tonight if I have time. But here's a log: ``` $ yarn add -D babel-plugin-module-resolver@beta eslint-import-resolver-babel-module@beta yarn add...

Sure! ```json { "parser": "vue-eslint-parser", "parserOptions": { "parser": "babel-eslint", "ecmaVersion": 2017, "sourceType": "module", "ecmaFeatures": { "modules": true, "jsx": true } }, "env": { "browser": true, "es6": true, "jquery": true, "jest/globals":...

It's a bit of a bloated mess. If you can't reproduce the problem then it's probably because of the vue parser. If it's still happening when both betas are released...

Oh sorry, of course. ```json { "presets": [ "flow", ["env", { "targets": { "browsers": [ "> 1%", "last 2 versions", "ie >= 9" ] }, "useBuiltIns": true, "debug": false, "modules":...

Oh it's because I overrode `extensions` without adding `.js` isn't it, sorry my mistake!

Yeah oops, thank you! Missed that it says it overrides it and not merges, my fault!

I had this issue too just a moment ago. I think it was an issue with my extension installation. Deleting the extension, restarting gnome-shell, and reinstalling seems to have fixed...

Again, mine is working now, so this is probably irrelevant, but here's mine in case it's a useful hint until @stuaxo is able to post his. View logs Nov 16...

Ah, looks like a dev-master tag exists that has it, that works!