ESLint error: Unable to resolve path to module '@hookform/resolvers'

See original GitHub issue

Shows an ESLint error says Unable to resolve path to module '@hookform/resolvers'. I can use the resolver without any issue, just a lint error.

Screen Shot 2020-07-07 at 2 10 43 PM

Issue Analytics

State:
Created 3 years ago
Comments:18 (12 by maintainers)

Top GitHub Comments

2reactions

bluebill1049commented, Jul 9, 2020

nice @snmgian thanks for saving all of us! publish the patch now.

1reaction

snmgiancommented, Jul 9, 2020

My app’s build process was running and ok, and the app was also running ok. Only eslint was complaining. When I faced those errors in the past, it was related to a package not being installed properly or not being installed at all.

As package.json tells where’s the file that is going to be imported, my first step was to look at the package.json. Then I found the missing dist/ path in jsnext:main.

As eslint-plugin-import uses jsnext:main entry, I tested it locally by fixing that path, run the linter again with no errors this time.

Top Results From Across the Web

Using eslint with typescript - Unable to resolve path to module

In my eslintrc.js config file, the "import/resolver" object needed to sit within the "rules" node, not the " ...

ESLint: Unable to resolve path to module #1180 - GitHub

I have solution for my other project (no RSK) with WebStorm: project_dir - Mark Directory as > Resource Root. yarn add eslint-import-resolver- ...

@hookform/resolvers - npm

A simple and composable way to validate data in JavaScript (or TypeScript). npm. import { useForm } from 'react-hook-form' ...

[Solved]-eslint + typescript + path in tsconfig: ESLint: Unable to ...

Coding example for the question eslint + typescript + path in tsconfig: ESLint: Unable to resolve path to module '@components/some-module'.

eslint/eslint - Gitter

I'm using parcel as a bundler, so I used eslint-import-resolver-parcel as ... 6:8 error Unable to resolve path to module '~/components' import/no-unresolved.