Better React 19 support

[chungweileong94]

What's new:

• Update the useFormState example to useActionState from React 19.
• prevState from form action is not undefined type by default.
• Added formData param in form action. As in React 19, <form> will be reset after the action is completed, in that case, we can use the formData to restore the form values, by returning the formData back to the client (Note: Only support in React 19, https://github.com/facebook/react/pull/28754)

[stackblitz[bot]]

Run & review this pull request in StackBlitz Codeflow.

[changeset-bot[bot]]

🦋 Changeset detected

Latest commit: 53d3860940e4c22c4819ea296597578effdc2495

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

| Name | Type | | ---------- | ----- | | server-act | Minor |

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[socket-security[bot]]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@types/react-dom@18.3.0	None	0	37.8 kB	types
npm/@types/react@18.3.2	None	+2	1.69 MB	types
npm/react-dom@19.0.0-beta-04b058868c-20240508	environment	+1	7.51 MB	react-bot
npm/react@19.0.0-beta-04b058868c-20240508	environment	0	379 kB	react-bot
npm/typescript@5.4.5	None	0	32.4 MB	typescript-bot

🚮 Removed packages: npm/@types/react-dom@18.2.14, npm/@types/react@18.2.33, npm/next@14.2.1, npm/react-dom@18.2.0, npm/react@18.2.0, npm/typescript@5.2.2

View full report↗︎

[socket-security[bot]]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/sharp@0.33.4

View full report↗︎

Next steps

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

[chungweileong94]

@SocketSecurity ignore npm/sharp@0.33.4