Tommy comments

Results 198 comments of


                                            Tommy

Support babel.config.js

Thanks for asking. I'll add it when time allows it :)

Support babel.config.js

Any idea why it falls to resolve in your project? Cause it would be great to fix this once and for all 🙂

Support babel.config.js

> However, some users or IDEs may run ESLint from somewhere other than the root of the project. For example, my understanding is that this is why options like babelrc...

Support babel.config.js

Yes please @tilgovi :) Thank you so much for investigating and finding a solution

not resolving node_modules, aliases or relative imports in vscode

Could you show me the structure of your project? If you have a public repo with the issue, I'd love to take a look

not resolving node_modules, aliases or relative imports in vscode

I bet this is some strange edge cases with the custom root being `"."`. Could you try removing it, but keeping your alias for the directories?

not resolving node_modules, aliases or relative imports in vscode

What do you mean by v2 vs v3?

not resolving node_modules, aliases or relative imports in vscode

Oh yes, indeed, in that case you cannot use the v3 beta version

not resolving node_modules, aliases or relative imports in vscode

It would be interesting to see if you have the issue while using the beta version for both the babel plugin and the eslint plugin, as we're moving towards this...

not resolving node_modules, aliases or relative imports in vscode

Thank you, I'll reopen and make some tests