You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you use SSR with vinxi 0.5.1 and build for prod, you get the infamous:
"React does not recognize the fetchPriority prop on a DOM element"
It appears to be added to assets passed for hydration. Other frameworks (Next.js) have fixed this with React 18.2 but this must need a fix here. Or it could be Nitro.
error in console with prod server:
Warning: React does not recognize the `fetchPriority` prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase `fetchpriority` instead. If you accidentally passed it from a parent component, remove it from the DOM element.
at link
at Suspense
at j (file://~/workspace/react/react-socket-prototype/.output/server/chunks/nitro/nitro.mjs:4465:778)
at Router (file://~/workspace/react/react-socket-prototype/.output/server/node_modules/react-router/dist/umd/react-router.development.js:1207:17)
at StaticRouter (file://~/workspace/react/react-socket-prototype/.output/server/node_modules/react-router-dom/server.mjs:11:3)
at div
at body
at html
If you use SSR with vinxi 0.5.1 and build for prod, you get the infamous:
"React does not recognize the
fetchPriority
prop on a DOM element"It appears to be added to assets passed for hydration. Other frameworks (Next.js) have fixed this with React 18.2 but this must need a fix here. Or it could be Nitro.
error in console with prod server:
see vercel/next.js#65161
The text was updated successfully, but these errors were encountered: