-
Notifications
You must be signed in to change notification settings - Fork 64
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
SvelteUI 1.0: A Complete Rewrite for Svelte 5 #491
Comments
Wow! |
Very exciting about the your update good timing, Svelte 5.0 will be very near |
I love it. The founder and team are passionate people. |
Thank you for all of your hard work. Looking forward to seeing this go live! |
Thank you very much for all your hard work. Now that Svelte 5 is officially released, do you have a timeline on this line of work? |
Starting to get concerned - seems like radio silence both here and on the SvelteUI discord. Is it time to start looking at replacement component libraries? I really don't want to, but I'm understandably concerned. |
Hey, the development has been stuck for a while, we haven't been able to find time to complete the migration. I saw the bug report with the error that's causing the library to be unusable with svelte 5, I'm going to take a look when I have some time. Hopefully we can fix that so that the lib is still usable while the migration is ongoing. |
Thanks for the update. |
Since Svelte 5 is now officially released and the default version for new projects, are there ideas how to make svelteui at least usable till the rewrite is done? Currently the svelte/internal call seems to break everything |
Working on it, but can't give a timeline yet |
@BeeMargarida perhaps you can find this patch useful (I rolled it to make TotalApp buildable with SvelteUI, and it seems to work under svelte 5) |
Dear SvelteUI users,
We're thrilled to announce that we're undertaking a complete rewrite of the SvelteUI library to take full advantage of the new features and improvements coming in Svelte 5 (in addition to the deprecation of our core styling engine). This decision wasn't taken lightly, but we believe it's necessary to ensure SvelteUI remains a robust, high-performance, and future-proof solution for building modern Svelte applications.
Why a Rewrite?
Svelte 5 introduces significant changes to the framework's architecture and API, some of which address long-standing issues and limitations that SvelteUI has faced. By rewriting the library from the ground up, we can:
What This Means for Users
During the rewrite process, the current
beta
version of SvelteUI (0.15.3
) will continue to be maintained and supported. However, new features and enhancements will be focused on the upcoming 1.0.0 release.We understand that a major version upgrade can be disruptive, but we're committed to making the transition as smooth as possible. As part of the 1.0.0 release, we'll provide comprehensive migration guides and documentation, as well as full support in the discord community
Timeline and Next Steps
We're currently in the alpha phase of SvelteUI 1.0, with a stable release planned for Q4 2024. If you'd like to get an early look at the new version and provide feedback, please check out the beta / preview branch.
We'll be sharing regular updates on the rewrite progress, as well as sneak peeks of new features and improvements, through our communication channels (e.g. GitHub Discussions, Reddit, Discord, etc.). Stay tuned!
Thank you for your continued support and patience as we work to make SvelteUI even better. We're excited about the future of Svelte and can't wait to share what we've been cooking up.
Let us know if you have any questions or concerns!
The SvelteUI Team 💙
The text was updated successfully, but these errors were encountered: