You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be a great move for Cloudscape components to support the (not so) new React Server Module Conventions v2. Many frameworks are now following this convention, making it difficult to use the components in an optimized way.
Quick fix (but not optimized)
At the moment, a simple hack is to create the following file and update your pages' imports. It makes all components 'Client Components', and should only be used as for compatibility issues. It will not make Cloudscape component 'Server Components'.
As far as I understand, server components is an experimental technology and the API is not stable yet (if there is a stable API, please provide a link).
We do not support experimental technologies. If you want to experiment with this technology, you can make necessary patches locally.
I am not sure the original ask to blindly add "use client"; all over our codebase is still valid, but if you have any compatibility issues, a new issue would be nice
Description
Hi everyone! 👋🏻
It would be a great move for Cloudscape components to support the (not so) new React Server Module Conventions v2. Many frameworks are now following this convention, making it difficult to use the components in an optimized way.
Quick fix (but not optimized)
At the moment, a simple hack is to create the following file and update your pages' imports. It makes all components 'Client Components', and should only be used as for compatibility issues. It will not make Cloudscape component 'Server Components'.
Click to reveal
Code of Conduct
The text was updated successfully, but these errors were encountered: