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

[minimaluminium]

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.

[bluebill1049]

Thanks @minimaluminium can you try to remove node_module and install it again? I don't see the issue at my end. Mabye that will resolve the problem.

[minimaluminium]

Hi. Removed node_modules and installed again, but same as before. I imported like below and the error is gone.

import {yupResolver} from '@hookform/resolvers/dist'

[bluebill1049]

hmmm this is strange.

[bluebill1049]

FYI @kotarella1110

[r-tae]

I'm getting a compile error that was also solved by that import:

./node_modules/@hookform/resolvers/dist/index.esm.js Attempted import error: 'appendErrors' is not exported from 'react-hook-form'.

Just thought I'd leave this comment in case it's somehow related...

[bluebill1049]

thanks @actual-size which version of RHF you are using?

[kotarella1110]

@minimaluminium please provide .eslintrc.js.

[r-tae]

@bluebill1049 RHF ^5.7.2 and @hookform/resolvers 0.0.5

[bluebill1049]

@actual-size v5 doesn't need resolver, resolver is for v6 :)

[minimaluminium]

@kotarella1110 Here it is.

{
  "extends": ["wesbos"],
  "rules": {
    "no-nested-ternary": 0,
    "prettier/prettier": [
      "error",
      {
        "semi": false,
        "bracketSpacing": false,
        "singleQuote": true
      }
    ]
  }
}

[fcrezza]

use validationSchema for v5

const schema = // your schema

const {register, handleSubmit} = useForm({
validationSchema: schema
})

[mrlubos]

Same issue and what @minimaluminium said fixed it, using react-hook-form 6.0.1. Could be related to using TypeScript?

[bluebill1049]

@mrlubos is it eslint as well?

[snmgian]

#23

[bluebill1049]

Thanks, heaps @snmgian I will release a patch now.

[bluebill1049]

before I close this, how did you find out it was due to that? @snmgian

[snmgian]

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.

[bluebill1049]

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