Replies: 1 comment
-
|
Agreed, and I think this goes beyond the Next.js/Turbopack issue — it's the silence that's the real concern. I'd love to use Keystatic in more of my projects, and even just a small update from the team would mean a lot to us all. 💜 EDIT: I'll take this back. A day after, plenty of PRs have been reviewed, thank you! ❤️ |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Context
Since the official response in Discussion #1442 (Aug 2025), @dcousens mentioned that Keystatic is actively maintained internally and that a community update with refreshed roadmaps would follow a new Keystone major release. That was ~7 months ago — no update has been published since.
Meanwhile:
@keystar/ui@0.7.19(keystar-ui-layout.js) that causesuseGridStyleProps is not a functionat runtime — making the entire Keystatic admin UI unusable under Turbopackmainwas Dec 15, 2025 (3+ months ago)Impact
For projects using
@keystatic/nextwith Next.js 16:next dev(Turbopack) → Keystatic admin is a white screen, zero console errorsnext dev --webpack→ works, but Webpack is now legacy in Next.js 16next build(Turbopack, default) → runtime crash on/keystaticThe only workaround is falling back to Webpack, which defeats the purpose of upgrading to Next.js 16.
Questions
@keystar/ui@0.7.20(or any release) to npm that fixes the Turbopack self-import issue?We understand open-source priorities shift — an honest status update would help the community make informed decisions. Thank you.
cc @JedWatson @emmatown @dcousens @jossmac
Beta Was this translation helpful? Give feedback.
All reactions