-
Notifications
You must be signed in to change notification settings - Fork 937
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
Support for Svelte/SvelteKit #6664
Comments
hi @bitcrshr , we have recently updated the entire system for building envs. for now we don't know if we'll build support for Svelt ourselves. if you are looking to maintain such env, please let us know and we can assist you in your efforts. |
Just dropping in here to show my support for this feature |
Yep, it would be a very nice feature! |
Hi All, Coming very soon... |
Couldn't quite grasp how to use the "teambit.svelte/svelte" env @benjgil is mentioning. Would love to know more if possible |
so what happened to svelte support? the mentioned link is dead and the docs also do not mention svelte. |
This was closed last year but it doesn't look like it was actually resolved. |
It's now available here https://bit.cloud/frontend/svelte I hope it will also appear soon in the docs, because they bypassed already Svelte component version 1.0.0 |
@mmailaender Do you know if it also works with SvelteKit? I would think so, as SvelteKit is just a full-stack wrapper around Svelte. |
Description
Our company uses SvelteKit for our web development, and we have a great interest in using Bit. As SvelteKit approaches a stable 1.0 release, and given its popularity already, I think it would be an amazing addition.
Describe the solution you'd like
Any support at all for using Bit with SvelteKit would be awesome. I am aware that there are guides floating around for how to create your own compiler to get Svelte components into Bit, but something 1st-party would be ideal (even if that means just writing your own guide for this without offering full-fledged support).
Describe alternatives you've considered
Writing a custom compiler does seem tempting, but for large, complicated projects, it seems far preferable to have official guidance from the Bit team.
The text was updated successfully, but these errors were encountered: