-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
Refines the language around server component stability to emphasize it's stability for user facing purposes #6782
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
a209c28
to
2bf1c33
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, can you also add it the the server-componets.md
and server-actions.md
pages?
Size changes📦 Next.js Bundle Analysis for react-devThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
2bf1c33
to
2a42399
Compare
2a42399
to
a1b6319
Compare
a1b6319
to
8920273
Compare
8920273
to
d11f84b
Compare
…s stable but the packages you work with as a framework and bundler will approach API stability
d11f84b
to
1ce5320
Compare
@rickhanlonii Think I got all your suggestions in |
Some feedback about the original post is that the line explaining stabilizing Server Components might imply the feature itself is unstable to use when we intend to communicate that the APIs a framework needs to integrate with might change outside of semver updates. This change clarifies the messaging