Thanks to visit codestin.com
Credit goes to github.com

Skip to content

useFormState does not work with JS disabled in edge runtime #56332

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
Closed
1 task done
Fredkiss3 opened this issue Oct 2, 2023 · 2 comments
Closed
1 task done

useFormState does not work with JS disabled in edge runtime #56332

Fredkiss3 opened this issue Oct 2, 2023 · 2 comments
Assignees
@shuding
Labels
bug Issue was opened via the bug report template. Pages Router Related to Pages Router. stale The issue has not seen recent activity.

Comments

@Fredkiss3
Copy link
Contributor

Link to the code that reproduces this issue

https://github.com/Fredkiss3/form-errors-pe/tree/repro/edge-runtime

To Reproduce

  1. Start the dev server
  2. disable JS in the devtools
  3. Submit the form without entering anything
  4. Nothing will show
  5. Now enable JS and submit the form still without entering anything
  6. You will see form errors appearing
  7. You can also test by just commenting the line export const runtime = 'edge' at the root layout and submitting the form with JS disabled
    8. -> Now you will see form errors appearing

Current vs. Expected behavior

The expected behavior is for useFormState to work with JS disabled but it doesn't work within edge runtime.

Verify canary release

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

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.0.0: Fri Sep 15 14:43:05 PDT 2023; root:xnu-10002.1.13~1/RELEASE_ARM64_T6020
Binaries:
  Node: 18.17.1
  npm: 9.6.7
  Yarn: 1.22.19
  pnpm: 8.7.1
Relevant Packages:
  next: 13.5.4-canary.9
  eslint-config-next: 13.4.19
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.2.2
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

App Router, Data fetching (gS(S)P, getInitialProps)

Additional context

No response
@Fredkiss3 Fredkiss3 added the bug Issue was opened via the bug report template. label Oct 2, 2023
@github-actions github-actions bot added the Pages Router Related to Pages Router. label Oct 2, 2023
@shuding shuding self-assigned this Oct 24, 2023
@nextjs-bot
Copy link
Collaborator

This issue has been automatically marked as stale due to two years of inactivity. It will be closed in 7 days unless there’s further input. If you believe this issue is still relevant, please leave a comment or provide updated details. Thank you.

@nextjs-bot nextjs-bot added the stale The issue has not seen recent activity. label Apr 21, 2025
@nextjs-bot
Copy link
Collaborator

This issue has been automatically closed due to two years of inactivity. If you’re still experiencing a similar problem or have additional details to share, please open a new issue following our current issue template. Your updated report helps us investigate and address concerns more efficiently. Thank you for your understanding!

@nextjs-bot nextjs-bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@shuding shuding

Labels
bug Issue was opened via the bug report template. Pages Router Related to Pages Router. stale The issue has not seen recent activity.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@shuding @Fredkiss3 @nextjs-bot