-
Notifications
You must be signed in to change notification settings - Fork 18
React 19 #2699
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
React 19 #2699
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
949b9e8 to
b35169d
Compare
| + element.style.pointerEvents = 'none'; | ||
| return element; | ||
| } | ||
| const $3db38b7d1fb3fe6a$export$be92b6f5f03c0fe9 = $3db38b7d1fb3fe6a$export$ac5b58043b79449b; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This patch isn't needed anymore because we now depend on a version of this library that incorporated our patch.
$ npm ls @radix-ui/react-focus-guards
oxide@0.0.0 /Users/david/oxide/console
└─┬ @radix-ui/react-dialog@1.1.6
└── @radix-ui/react-focus-guards@1.1.1
| -RemoveScroll.classNames = { | ||
| - fullWidth: fullWidthClassName, | ||
| - zeroRight: zeroRightClassName, | ||
| -}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This existing bit of the patch wasn't necessary. These lines do not set classes, they set a value RemoveScroll.classNames that is imported by other things and used for stuff.
|
The |
I went through the v5 migration guide and confirmed there was nothing we actually needed to change. https://github.com/pmndrs/zustand/blob/c9330941c8bad6add1c95bb69099c39606151abd/docs/migrations/migrating-to-v5.md
| <form className="flex"> | ||
| <Listbox | ||
| className="z-10 w-[10rem] border-r border-r-default [&>button]:!rounded-r-none [&>button]:!border-r-0" | ||
| className="z-10 w-[10rem] border-r border-r-default [&_button]:!rounded-r-none [&_button]:!border-r-0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| // work at the same time (so that, for example, in theory, a button could be | ||
| // simultaneously disabled with a tooltip *and* be focused programmatically [I | ||
| // tested this]), we merge the two refs inside Tooltip, using child.props.ref to | ||
| // get the original ref on the button. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
important comment added
charliepark
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All of this is looking good to me locally
oxidecomputer/console@7de4b11...dc4e0d4 * [dc4e0d4f](oxidecomputer/console@dc4e0d4f) oxidecomputer/console#2712 * [381f374f](oxidecomputer/console@381f374f) oxidecomputer/console#2711 * [32636781](oxidecomputer/console@32636781) oxidecomputer/console#2654 * [a72b460c](oxidecomputer/console@a72b460c) delete unused metrics utils * [3dd06294](oxidecomputer/console@3dd06294) add npm run start:colo * [f591c282](oxidecomputer/console@f591c282) oxidecomputer/console#2707 * [3b838e0b](oxidecomputer/console@3b838e0b) oxidecomputer/console#2706 * [74005f8d](oxidecomputer/console@74005f8d) oxidecomputer/console#2702 * [e8371db1](oxidecomputer/console@e8371db1) make debug ci e2e trace script more flexible * [27e0c130](oxidecomputer/console@27e0c130) oxidecomputer/console#2705 * [db94deab](oxidecomputer/console@db94deab) oxidecomputer/console#2703 * [6ed7d862](oxidecomputer/console@6ed7d862) oxidecomputer/console#2701 * [ba3ab97d](oxidecomputer/console@ba3ab97d) oxidecomputer/console#2699 * [c14b4afa](oxidecomputer/console@c14b4afa) oxidecomputer/console#2693
oxidecomputer/console@7de4b11...dc4e0d4 * [dc4e0d4f](oxidecomputer/console@dc4e0d4f) oxidecomputer/console#2712 * [381f374f](oxidecomputer/console@381f374f) oxidecomputer/console#2711 * [32636781](oxidecomputer/console@32636781) oxidecomputer/console#2654 * [a72b460c](oxidecomputer/console@a72b460c) delete unused metrics utils * [3dd06294](oxidecomputer/console@3dd06294) add npm run start:colo * [f591c282](oxidecomputer/console@f591c282) oxidecomputer/console#2707 * [3b838e0b](oxidecomputer/console@3b838e0b) oxidecomputer/console#2706 * [74005f8d](oxidecomputer/console@74005f8d) oxidecomputer/console#2702 * [e8371db1](oxidecomputer/console@e8371db1) make debug ci e2e trace script more flexible * [27e0c130](oxidecomputer/console@27e0c130) oxidecomputer/console#2705 * [db94deab](oxidecomputer/console@db94deab) oxidecomputer/console#2703 * [6ed7d862](oxidecomputer/console@6ed7d862) oxidecomputer/console#2701 * [ba3ab97d](oxidecomputer/console@ba3ab97d) oxidecomputer/console#2699 * [c14b4afa](oxidecomputer/console@c14b4afa) oxidecomputer/console#2693

Redoing #2636 without needing to use
overridesinpackage.jsonby updating some deps and fixing the react peer deps in@oxide/design-system(oxidecomputer/design-system#118) and@oxide/react-asciidoc(oxidecomputer/react-asciidoc#32).Most of our type errors are due to
ReactElement's props generic changing fromanytounknown. See https://react.dev/blog/2024/04/25/react-19-upgrade-guide#changes-to-the-reactelement-typescript-type. This is clearly more correct, and forces us to fix some things we were doing unsafely, but it is annoying.npm installto not blow up@radix-ui/react-focus-guardspatch because we now depend on a version of this library that incorporated our patchreact-remove-scrollpatch — we accidentally have two versions installed and we are patching the wrong one! (see use a content-security-policy in development #2142)data-headlessui-statesupplied toReact.Fragment" warnings on many pages (presumably due to passing a fragment to a headless UI thing that should be a div or something)Effect on bundle size
A little bigger. I think a small increase is expected, but I'm not sure exactly how much. I plan to mitigate this anyway very soon by switching to RRv7 framework mode, which automatically code-splits every route.
Before
After