Closed jasonnoahchoi closed 1 year ago
Came here to make an issue for the following, but looks related to this - something wrong with Clerk getServerSideProps on the homepage?
On a fresh CUA via npx create-t3-universal-app
, after setting up env variables, running yarn desktop
fails with "pages with getServerSideProps
can not be exported":
nextjs:dev:tauri: Error occurred prerendering page "/". Read more: https://nextjs.org/docs/messages/prerender-error
nextjs:dev:tauri: Error: Error for page /: pages with `getServerSideProps` can not be exported. See more info here: https://nextjs.org/docs/messages/gssp-export
nextjs:dev:tauri: at /Users/{...}/node_modules/next/dist/export/worker.js:245:23
nextjs:dev:tauri: at async Span.traceAsyncFn (/Users/{...}/node_modules/next/dist/trace/trace.js:79:20)
nextjs:dev:tauri: info - Exporting (8/8)
nextjs:dev:tauri: Error: Export encountered errors on following paths:
nextjs:dev:tauri: /
nextjs:dev:tauri: at /Users/{...}/node_modules/next/dist/export/index.js:409:19
nextjs:dev:tauri: at processTicksAndRejections (node:internal/process/task_queues:96:5)
nextjs:dev:tauri: at async Span.traceAsyncFn (/Users/{...}/next/dist/trace/trace.js:79:20)
nextjs:dev:tauri: Error The "beforeDevCommand" terminated with a non-zero status code.
I'm not too sure why getServerSideProps is breaking it in this case, if someone can make it work I'd love a PR! But for now I've reverted the PR that causes the issue!
Came here to make an issue for the following, but looks related to this - something wrong with Clerk getServerSideProps on the homepage?
On a fresh CUA via
npx create-t3-universal-app
, after setting up env variables, runningyarn desktop
fails with "pages withgetServerSideProps
can not be exported":nextjs:dev:tauri: Error occurred prerendering page "/". Read more: https://nextjs.org/docs/messages/prerender-error nextjs:dev:tauri: Error: Error for page /: pages with `getServerSideProps` can not be exported. See more info here: https://nextjs.org/docs/messages/gssp-export nextjs:dev:tauri: at /Users/{...}/node_modules/next/dist/export/worker.js:245:23 nextjs:dev:tauri: at async Span.traceAsyncFn (/Users/{...}/node_modules/next/dist/trace/trace.js:79:20) nextjs:dev:tauri: info - Exporting (8/8) nextjs:dev:tauri: Error: Export encountered errors on following paths: nextjs:dev:tauri: / nextjs:dev:tauri: at /Users/{...}/node_modules/next/dist/export/index.js:409:19 nextjs:dev:tauri: at processTicksAndRejections (node:internal/process/task_queues:96:5) nextjs:dev:tauri: at async Span.traceAsyncFn (/Users/{...}/next/dist/trace/trace.js:79:20) nextjs:dev:tauri: Error The "beforeDevCommand" terminated with a non-zero status code.
I believe this is due to this commit. We should probably revert it since tauri doesn't support ssr. Try without any getServerSideProps in your codebase.
I believe this issue is fixed by #61, reverting #51.
Describe the bug I haven't investigated too much about why this is happening, but no matter what I was doing, the project runs fine locally, but I just couldn't get builds to work on vercel or if I run
yarn build
.To Reproduce Steps to reproduce the behavior:
yarn
yarn build
OR deploy to vercelExpected behavior A clear and concise description of what you expected to happen. I expect the page to render without an internal server error
Screenshots If applicable, add screenshots to help explain your problem. I believe the demo project is likely the same. I'm sure if you undo PR #51 cua-demo.vercel.app will render again.
Desktop (please complete the following information):
Smartphone (please complete the following information):