-
Notifications
You must be signed in to change notification settings - Fork 401
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Webpack + ESLint: "unable to resolve path to module .." (import/no-unresolved) #1419
Comments
Having the same issue after upgrading |
Since Hound doesn't install the extensions and packages locally, the path cannot be resolved. We recommend disabling this rule in your |
changes as [suggested by hound maintainer](houndci/hound#1419)
changes as [suggested by hound maintainer](houndci/hound#1419)
I found this answer in stack overflow for ESLint |
I solved this issue by editing my tsconfig.json and adding:
also in eslintrc:
inside my federated-module.d.ts, it had the declare module, etc for the missing types. |
I'm getting a lot of "unable to resolve path to module .." errors when Hound lints my code. After invest a lot of time to resolve this error without any luck, i hope anybody else has an idea how to resolve this. Are there more people who experience this?
Currently i'm working in a ruby 2.4.1 with rails 5.0.4 environment and I'm using webpack to compile my javascript. I read a lot about the "eslint-import-resolver-webpack" to solve this problem. Locally ESLint with the webpack resolver works fine with my Editor (VS Code) and via the CLI.
I'm using the following versions:
with this
.eslintrc.yml
configuration:and the following webpack alias resolver:
The text was updated successfully, but these errors were encountered: