Share Your Feedback on Vibes Components in Catalyst #2001
katiehoesley
started this conversation in
General
Replies: 1 comment 5 replies
-
|
The introduction of Vibes components has certainly improved our performance. However, our biggest challenge has been tracking the breaking changes on Catalyst and synchronizing them with our modified version. We immediately began creating our own Vibes components and kept the core in sync with the Catalyst canary, but it felt like it came out of nowhere before the full v1.0 release. We've been working hard to keep up, resulting in the creation of many fallback components 😄 |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hey devs!
As we continue refining Catalyst, we’d love your input on how the Vibes components are shaping your development experience. Your insights will help us improve usability, extensibility, and overall efficiency.
A few quick questions for you:
💥How has your experience been working with Vibes components so far? (Any frustrations or wins?)
💥How has your implementation approach changed since adopting Vibes components? (Easier? More restrictive? More flexible?)
💥How does this abstraction layer impact your ability to extend and customize components for your needs?
Your feedback is invaluable—drop your thoughts on this discussion!
Looking forward to your insights!
Beta Was this translation helpful? Give feedback.
All reactions