T
TanStack•3y ago
afraid-scarlet

Run build / Deploy to Vercel Failing

My build / deploy is failing with: Error: Not implemented. I'm essentially following these docs to the T: https://tanstack.com/query/v4/docs/react/guides/ssr#using-hydrate Vercel deploy logs: https://pastebin.com/tBeuTGH1 here are my pnpm run build logs: https://pastebin.com/mv0QsZf2 Code: https://github.com/currenthandle/okay_bears/blob/main/src/utils/getQueryClient.tsx What's going on here? What am I missing?
6 Replies
extended-yellow
extended-yellow•3y ago
Are you deploying to the edge?
afraid-scarlet
afraid-scarletOP•3y ago
idk Unless it's the default, almost certainly no Again the issue happens when I run pnpm run build before I deploy so I don't think that's the issue....
extended-yellow
extended-yellow•3y ago
your log shows react-dom-server.edge.production.min, that's why I asked:
at Je (/vercel/path0/node_modules/.pnpm/next@13.4.7_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/react-dom/cjs/react-dom-server.edge.production.min.js:121:272)
at Je (/vercel/path0/node_modules/.pnpm/next@13.4.7_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/react-dom/cjs/react-dom-server.edge.production.min.js:121:272)
afraid-scarlet
afraid-scarletOP•3y ago
All good, I'm just following the most basic Vercel deploy. (1) push to GH (2) add project in Vercel (3) watch it build. @TkDodo 🔮 like I said, I following the TanStack almost identically but these seems to be and issue with React.cache. Can you confirm that the react-query guide for prefetching in next 13 /app directory is deployable to Vercel? :https://tanstack.com/query/v4/docs/react/guides/ssr#using-the-app-directory-in-nextjs-13 There appears to be an issue with React.cache in vercel: https://stackoverflow.com/questions/76370924/nextjs-error-not-implemented-when-using-cache?noredirect=1#comment135017830_76370924
extended-yellow
extended-yellow•3y ago
I can't help if vercel has issues 😅
graceful-blue
graceful-blue•3y ago
Where you ever able to solve this? I'm having the same issue. Locally too

Did you find this page helpful?