-
Notifications
You must be signed in to change notification settings - Fork 91
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
Embedded Sanity displays blank page when using --turbo #1621
Comments
Hello, can you attach the trace file content? To generate a trace file - .next/trace.log |
The trace.log file was about 177MB, so I uploaded it to dropbox since GitHub only supports file uploads up to 25MB. |
Hi, could you try the latest canary? |
Installed
|
Currently getting the same issue with next 15-rc and react 19-rc, when using |
Same problem. Any updates? more details |
Confirming the problem still exists. A temporary "fix" is to remove —turbo as described above, but I guess removing turbo is not the idea of using turbo hmm. Tested with moving the sanity config in another project; tested even by cloning this repo as-is (which throws other errors). |
Describe the bug
I'm using Next.js with an embedded Sanity Studio that is accessible at the
/studio
route. When I usenext dev
to do local development the studio functions correctly. However, when I usenext dev --turbo
I get a blank page with no visible errors in the browser console or terminal output.To Reproduce
npx create-next-app next-sanity-starter
and go with the defaults as prompted.cd next-sanity-starter
.npx sanity init
and setup an empty project that uses/studio
for the route.npx next dev
.http://localhost:3000/studio
and notice that it loads successfully.npx next dev --turbo
http://localhost:3000/studio
and notice that it displays a blank page.Expected behavior
The studio renders the default landing page.
Screenshots
Which versions of Sanity are you using?
What operating system are you using?
macOS Sonoma 14.5
Which versions of Node.js / npm are you running?
The text was updated successfully, but these errors were encountered: