Cannot get existing tests passing in @hookform/resolvers repo (Contributing)

[novacoole]

So I am trying to create a new resolver to handle ElysiaJS's extension of TypeBox schemas.

I could not get tests running in the @hookform/resolvers repo and eventually realised they will hang when using Vitest version 3.0.9 even though the package.json currently specifies:
"vitest": "^3.0.9",

I can now get the tests to run using bun run test (CONTRIBUTING.md currently says bun test which does not work) but I get these results on tag v5.2.2:

 Test Files  18 failed | 49 passed (67)
      Tests  44 failed | 213 passed (257)

Many of these failing tests are due to the same underlying issue:

stderr | arktype/src/__tests__/arktype.ts > arktypeResolver > should correctly infer the output type from a arktype schema for the handleSubmit function in useForm
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://react.dev/link/invalid-hook-call for tips about how to debug and fix this problem.

I am guessing bun has just installed the incorrect version of some testing package, but I can't really understand how these tests would ever pass in a development environment without the use of something like renderHook from react-testing-library.

Any help would be greatly appreciated, I'd love to contribute to this project.

[ryux1]

You weren't missing a local setup step: v5.2.2 genuinely had a broken test baseline.

The invalid-hook-call failures came from tests calling useForm() directly. Those calls were later wrapped with Testing Library's renderHook(). The repo also corrected bun test to bun run test, because the former invokes Bun's own runner rather than the package's Vitest script.

These fixes were merged in react-hook-form/resolvers#854 and released in v5.4.3. That PR also restored the test step in CI; tests had not been running there since #699.

For a new resolver contribution, start from current master (or at least a release after v5.4.3), then run:

bun install
bun run test
bun lint
bun run build

Current CI is green with the test stage enabled, so rebasing away from v5.2.2 should remove the baseline failures and leave only failures related to your resolver, if any.