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.

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

An error occurred when using the third-party library async-validator in Nextjs #55933

Closed
1 task done
shaxutang opened this issue Sep 25, 2023 · 2 comments
Closed
1 task done
Labels
examples Issue/PR related to examples locked

Comments

@shaxutang
Copy link

Verify canary release

  • I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Home China
Binaries:
  Node: 18.17.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 13.5.3-canary.3
  eslint-config-next: 13.5.2
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.2.2
Next.js Config:
  output: N/A

Which example does this report relate to?

with-turbo

What browser are you using? (if relevant)

Chrome 117.0.5938.92

How are you deploying your application? (if relevant)

vercel

Describe the Bug

I created a project using the turbo example design-system, in the ui module. I introduced the third-party library async-validator, but I got an error when using it.
image
image
image

Expected Behavior

I hope async-validator can be used normally in nextJs

To Reproduce

I tried many ways, but in the end I found that after adding the following configuration to package.json under the ui module, this error will appear. If I delete it, everything will be normal.
image
Currently, this problem is only found in nextjs, but not in vite.

repo: https://github.com/shaxutang/next-asynv-validator-bug

@shaxutang shaxutang added the examples Issue/PR related to examples label Sep 25, 2023
@balazsorban44
Copy link
Member

After some digging, this seems to be an upstream issue, see yiminghe/async-validator#312

@github-actions
Copy link
Contributor

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 13, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
examples Issue/PR related to examples locked
Projects
None yet
Development

No branches or pull requests

2 participants