-
Notifications
You must be signed in to change notification settings - Fork 31
Re-Opening Issue 36 #40
Comments
Sorry about that @machineghost. Let's find out what is causing your issue :) First, let's remove the alias/root config set in your eslint config. The one from the babel plugin will be used anyway. Then it seems you can replace your babel config with this one:
Having both root and alias shouldn't conflict, but it will be easier to remove any extras :) Do you think you could build a small repo with your eslint and babel config, while replacing your files by dummy files? (Only the relevant paths are fine. The content doesn't really matter) |
https://github.com/machineghost/eslint-import-resolver-babel-module-issues-40 Run
|
In your demo, the root config is not properly set. It should be |
Sorry about that (side effect of simplifying a more complex project). I've corrected the demo repo. |
I got it working yesterday when I tried so I thought it was the only issue. After removing the old plugins (module-alias) and upgrading to these 2 versions, everything is fine.
|
That was the problem, thanks so much and sorry for bothering you. |
No worries :) Glad I was able to help! |
I originally created issue #36, but it was closed without resolving my underlying problem. While I'm sure it solved a different issue, my issue (even after installing the latest version, 3.10.10) unfortunately remains.
One again here are my relevant bits from my relevant files ...
.eslintrc:
.babelrc
However, when I ESlint a file (a file that can successfully import
module-resolver
-resolved paths using Babel just fine) I get:... even though
src/components/ui/countryPicker/CountryGroup
exists, and even though I have both"root": ["./src"],
and"alias": {"components": "./frontend/src/components",
in both my.babelrc
and my.eslintrc
.Any help resolving this would be appreciated. As before, unfortunately I can't share a repository of my entire project (because I'd be fired if I did), but if there is any other relevant information (debug logs, copies of other config files, etc.) I'd be happy to provide it.
The text was updated successfully, but these errors were encountered: