-
Notifications
You must be signed in to change notification settings - Fork 27
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
✨ feat(SSR): add for next projects #1478
base: main
Are you sure you want to change the base?
✨ feat(SSR): add for next projects #1478
Conversation
Upgarde stencil core to v4.21.0. This is need because we need the new features inside the generated hydration script.
…d hydration script
# Conflicts: # package-lock.json
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Someone is attempting to deploy a commit to the baloise Team on Vercel. A member of the Team first needs to authorize it. |
🚀 Welcome to Baloise ChatOps based GitOps Bot 🎉
|
Add SSR Support for Next.js - Hydration Issues
Description:
This PR introduces a draft version of server-side rendering (SSR) support for Next.js in the Baloise design system. While I've made progress in implementing SSR, there are still a few issues I couldn't resolve myself.
Current Issues:
Next.js is throwing warnings and errors during the hydration process.
The primary issue is that the HTML generated on the server does not match the HTML on the client, leading to hydration failures.
As a result, the client-side app is not able to hydrate the server-rendered content correctly, causing the mismatch.
Since I’ve been unable to fully fix these issues, I'm opening this PR so you can review the implementation and provide guidance on resolving these problems.
Steps Taken So Far:
Integrated SSR within the Next.js framework.
Attempted to address hydration discrepancies but ran into persistent errors.
I would appreciate any insights or suggestions to help resolve these issues and improve SSR support for the design system.