How do I migrate from gluestack v1 to v2?
- We have a detailed migration guide with codemod.
Will gluestack v2 be compatible with my current project?
- Yes, you need to follow a few steps to get your project up and running.
What are the major differences between gluestack v1 and v2?

gluestack-v1	gluestack-v2
Bundled Library	Copy-Pastable components
gluestack-style as styling library	NativeWind as a styling library
Utility prop support	Tailwind CSS className support
No RSC support	Partial RSC support

New Features and Improvements

What are the new features in gluestack v2?
- Tailwind CSS className support.
- Partial RSC support.
- NativeWind as a styling library.
- Copy-Pastable components.
How does gluestack v2 improve performance compared to v1?
- Coming soon...
Are there any new components or APIs in gluestack v2?
- Yes, we have Skeleton, Table, Bottomsheet, Grid, and many more to come.

Support and Community

What kind of support is available for gluestack v1?
- We will provide maintenance and support for gluestack-ui v1 for a limited time to ensure a smooth transition.
How can I provide feedback or report bugs?
- You can create a GitHub issue on our repo.

Are there any known issues with gluestack v2?
- You can check out the troubleshooting page for this.
Are there any deprecated features from v1 that are not available in gluestack v2?
- Descendant Styling.
- Utility Props.
- Property Resolver.
- Passing Prop.

How do I integrate gluestack v2 with other libraries and frameworks?
- It works out of the box. You can check out our integration of Gorhom Bottom Sheet for more reference.
What are the best practices for using gluestack v2 in production?
- Purge Unused CSS: Enable PurgeCSS to remove unused styles in production.
- Use CDN for Tailwind: Serve Tailwind CSS via a CDN for faster load times.
- Optimize Build Process: Use tools like PostCSS and Autoprefixer for better performance.
- Minimize Custom CSS: Stick to Tailwind's utility classes to keep your CSS file small.
- Don't Include Unused Utilities: Avoid adding unused utilities in your configuration to keep the CSS file lightweight.
- Don't Ignore Responsive Design: Ensure your design is responsive to avoid performance issues on different devices.
- Don't Overload with Plugins: Use only necessary plugins to avoid bloating the CSS file.
- Don't Skip Testing: Regularly test your site's performance and make adjustments as needed.