jaredpalmer
Make typings compatible with v19
Fixes #4011.
To test this, I ran yarn install locally and verified that the aforementioned dist files no longer reference global JSX, but use React.JSX instead.
⚠️ No Changeset found
Latest commit: b405a5d83de13bcb567d160a13a702e9893c297f
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
![changeset-bot[bot] avatar](https://avatars.githubusercontent.com/in/28616?v=4 "Published by a pub.dev verified publisher"){kind=small}
The latest updates on your projects. Learn more about Vercel for Git ↗︎
| Name | Status | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| formik-docs | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Dec 7, 2024 3:28pm |
![vercel[bot] avatar](https://avatars.githubusercontent.com/in/8329?v=4 "Published by a pub.dev verified publisher"){kind=small}
This pull request is automatically built and testable in CodeSandbox.
To see build info of the built libraries, click here or the icon next to each commit SHA.
![codesandbox-ci[bot] avatar](https://avatars.githubusercontent.com/in/38409?v=4 "Published by a pub.dev verified publisher"){kind=small}
@jaredpalmer @quantizor Could you please take a look? The PR seems to be very small to review
@jaredpalmer @quantizor @eonwhite Due to recent vulnerabilities in the Next.js Image API, many users are being forced to upgrade to the latest 15.x version of Next.js, which requires React 19. However, Formik is not currently compatible :/
I can confirm that with these changes, everything seems to be working (at least it's compiling my Next app and there are no obvious issues).
I sent a message to @quantizor on X.com (already tried to reach @jaredpalmer on X and his email, no answer currently)
For those waiting for this PR to be merged, I suggest using the proper approach — the patch command provided by your package manager (e.g., yarn patch) — and applying this PR as the patch base.
@jaredpalmer don't know what happened here but it seems there is still issues on the last release