Skip to content
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

fix(editor): allow state to be undefined/null in SerloRenderer #4302

Merged

Conversation

LarsTheGlidingSquirrel
Copy link
Member

No description provided.

Copy link

vercel bot commented Nov 20, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
frontend 🔄 Building (Inspect) Visit Preview Nov 20, 2024 6:27am

@LarsTheGlidingSquirrel LarsTheGlidingSquirrel merged commit 98f2f76 into staging Nov 20, 2024
8 of 9 checks passed
@LarsTheGlidingSquirrel LarsTheGlidingSquirrel deleted the allow-nullish-state-in-serlo-renderer branch November 20, 2024 06:30
Copy link
Contributor

📦 Next.js Bundle Analysis for @serlo/frontend

This analysis was generated by the Next.js Bundle Analysis action. 🤖

🎉 Global Bundle Size Decreased

Page Size (compressed)
global 104.73 KB (-4 B)
Details

The global bundle is the javascript bundle that loads alongside every page. It is in its own category because its impact is much higher - an increase to its size means that every page on your website loads slower, and a decrease means every page loads faster.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

If you want further insight into what is behind the changes, give @next/bundle-analyzer a try!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant