Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Error when Trying to Use Arktype Resolver #693

Closed
lucaschultz opened this issue Jun 18, 2024 · 6 comments · Fixed by Sourav-Goyal19/Finance-Manager#2, carltrepanier/threads_clone#190, leoo1992/sistema_ponto#31, codu-code/codu#980 or zntb/next-auth-v5-tutorial#10
Closed

Error when Trying to Use Arktype Resolver #693

lucaschultz opened this issue Jun 18, 2024 · 6 comments · Fixed by Sourav-Goyal19/Finance-Manager#2, carltrepanier/threads_clone#190, leoo1992/sistema_ponto#31, codu-code/codu#980 or zntb/next-auth-v5-tutorial#10

Comments

@lucaschultz
Copy link

Describe the bug
When trying to use the arktypeResolver the following error happens:

Error: Tried to initialize an $ark registry but one already existed.
This probably means you are either depending on multiple versions of an arktype package,
or importing the same package from both ESM and CJS.
Review package.json versions across your repo to ensure consistency.

To Reproduce
Steps to reproduce the behavior:

  1. Call the useForm hook with the arktypeResolver as resolver.

Codesandbox link (Required)
No Codesandbox link, but I created a minimal reproduction using Next.js here, but the error happened in a Vite/React app I'm working on. @ssalbdivad you might wanna have a look 😊

Expected behavior
Being able to use the provider, regardless if the project is ESM or not.

Screenshots

Bildschirmfoto 2024-06-18 um 12 28 05

Desktop (please complete the following information):

  • OS: macOS
  • Browser: Chrome
  • Version: 125.0.6422.114
@ssalbdivad
Copy link
Contributor

Thanks for letting me know! This issue should be opened in the ArkType repo instead.

Happy to investigate what might be going wrong there!

@lucaschultz
Copy link
Author

This issue should be opened in the ArkType repo instead.

@ssalbdivad ah yes, I was wondering where to open the issue. Settled on this repository because the error message lead to be believe the issue might be that using the resolver creates another registry which somehow collides with the other one, so I assumed the problem might be one of the resolver rather than with Arktype itself.

Should I open a copy in the Arktype repo?

@lucaschultz lucaschultz mentioned this issue Jun 19, 2024
Closed
@jorisre
Copy link
Member

jorisre commented Jul 2, 2024 •
edited
Loading

Closing in favor fo arktypeio/arktype#1022

@jorisre jorisre closed this as completed Jul 2, 2024
@jorisre jorisre reopened this Jul 2, 2024
@jorisre jorisre mentioned this issue Jul 2, 2024
Merged
@jorisre
Copy link
Member

jorisre commented Jul 2, 2024 •
edited
Loading

I made some changes to improve bundle size in #699. Hopefully, it will fix this issue in the next release.

jorisre added a commit that referenced this issue Jul 4, 2024
@jorisre @decs @bluebill1049
feat: add typeschema resolver (#699)
18e423f 
* feat(typeschema): add typeschema resolver

* fix(arktype): exclude arktype from resolver bundle (#693)

* perf(valibot): reduce bundle size

* perf(vine): reduce bundle size

* chore(deps): update dependencies

* chore: migrate to Bun & Biome



---------

Co-authored-by: Trent Cox <[email protected]>

* Update node version (#680)

* Update main.yml (#681)

* perf(typeschemaResolver): save some bytes

* perf(arktype): reduce bundle size

* perf: reduce bundle size

* chore: update deps

* chore: update all deps

---------

Co-authored-by: André Costa <[email protected]>
Co-authored-by: Trent Cox <[email protected]>
Co-authored-by: Beier (Bill) <[email protected]>
@jorisre
Copy link
Member

jorisre commented Jul 5, 2024

@lucaschultz Can you try with the last version (3.8.0)?

@jorisre
Copy link
Member

jorisre commented Jul 6, 2024

I looked at the example you provided to reproduce the issue in Next.js and updated the @hookform/resolvers package to its latest version (3.9.0). The problem is now fixed. Thank you for reporting the issue. I'm closing this issue since it's been resolved.

@jorisre jorisre closed this as completed Jul 6, 2024
@Sourav-Goyal19 Sourav-Goyal19 mentioned this issue Jul 27, 2024
Merged
@carltrepanier carltrepanier mentioned this issue Jul 27, 2024
Merged
@leoo1992 leoo1992 mentioned this issue Jul 27, 2024
Merged
@NiallJoeMaher NiallJoeMaher mentioned this issue Aug 1, 2024
Merged
This was referenced Aug 2, 2024
Closed
Merged
This was referenced Aug 16, 2024
Merged
Merged
Merged
This was referenced Aug 21, 2024
Open
Open
Open
@SanteriMertakorpi SanteriMertakorpi mentioned this issue Aug 24, 2024
Merged
@onsails onsails mentioned this issue Aug 29, 2024
Open
This was referenced Sep 13, 2024
Closed
Closed
Closed
Closed
This was referenced Sep 17, 2024
Closed
Closed
Closed
@varensev varensev mentioned this issue Sep 24, 2024
Open
@Nakamura1121 Nakamura1121 mentioned this issue Sep 30, 2024
Open
@snyk-io snyk-io bot mentioned this issue Oct 27, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Snyk] Upgrade @hookform/resolvers from 3.8.0 to 3.9.0 Sourav-Goyal19/Finance-Manager
[Snyk] Upgrade @hookform/resolvers from 3.7.0 to 3.9.0 carltrepanier/threads_clone
[Snyk] Upgrade @hookform/resolvers from 3.7.0 to 3.9.0 leoo1992/sistema_ponto
[Snyk] Upgrade @hookform/resolvers from 3.6.0 to 3.9.0 codu-code/codu
[Snyk] Upgrade @hookform/resolvers from 3.3.4 to 3.9.0 zntb/next-auth-v5-tutorial
[Snyk] Upgrade @hookform/resolvers from 3.3.4 to 3.9.0 zntb/nextjs-lucia-auth
[Snyk] Upgrade @hookform/resolvers from 3.3.4 to 3.9.0 zntb/nextjs-web3-app-zksync
[Snyk] Upgrade @hookform/resolvers from 3.3.4 to 3.9.0 zntb/mern-food-ordering-app-frontend
[Snyk] Upgrade @hookform/resolvers from 3.4.2 to 3.9.0 SanteriMertakorpi/Password-Manager
OPHJOD-851: Upgrade @hookform&#x2F;resolvers from 3.4.2 to 3.9.1 Opetushallitus/jod-yksilo-ui
3 participants
@jorisre @ssalbdivad @lucaschultz