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
First of, thanks a ton to all the contributors for this project! This library has made so much work easier for us and is essential for the svelte ecosystem to grow, as this is and will become the base for many SaaS tools/projects ahead.
The last update to this library was Jul 20 and issues #444 make it not possible to use it with Svelte 4. I was curious to know if any more work is planned on this library and if I can help in any way. Thanks a looking forward to many more releases ahead!
The text was updated successfully, but these errors were encountered:
I'd also like to know as we are building a new product which will leverage this, if the developers are not going to maintain we would rather save ourselves the technical debt now.
My 2 cts.
I did my best to manage to use Svelvet in my app by creating issues, PR and even a fork with various contributions as well as a custom npm package build. The announcement of Svelte Flow a month ago was a great surprise, the migration of my code was relatively simple. The result is awesome, stable and clear code.
Svelvet 9 was released on 16th November and they are working on Svelvet 10. So svelvet is still in active development.
I think the issue is, that svelvet is not developed by a Core Team rather then volunteers on a rotating basis leading to no consistent Issue and PR Management.
First of, thanks a ton to all the contributors for this project! This library has made so much work easier for us and is essential for the svelte ecosystem to grow, as this is and will become the base for many SaaS tools/projects ahead.
The last update to this library was Jul 20 and issues #444 make it not possible to use it with Svelte 4. I was curious to know if any more work is planned on this library and if I can help in any way. Thanks a looking forward to many more releases ahead!
The text was updated successfully, but these errors were encountered: