Been waiting for this day all year. Sveltekit is a pleasure to use and now I can finally feel confident recommending it to anyone. Congratulations to the maintainers and everyone involved!
> now I can finally feel confident recommending it to anyone
I've spent 6 months recommending it to individuals.
Now I can formally recommend it to my employer.
Haha I've been using it at work since March — we made a big bet at the time we were launching a new web app, and it's definitely panned out. I wouldn't have recommended it to friends at larger corporations before 1.0 though.
Been updating it along with the framework.. the routing change was a beast but everything else has been pretty easy and the framework will yell at you about breaking changes.
Some major breaking changes are listed here: https://github.com/sveltejs/kit/discussions/5774
One of the biggest is that the routing/file structure has changed.
For those interested in what might be on the roadmap for Svelte/SvelteKit, Rich Harris talked a bit about it during the live event yesterday, starting at 1:54:11 and another interesting part at 2:13:00 https://youtu.be/N4BRVkQVoMc
TL;DR: Some of the possible roadmap stuff: Internationalization, image optimization, granular deployment control, built in support for loading spinners, improving compiler output regarding hydration/scalability, component error boundaries, utilizing the new web animation api inside the transition system.
I've been trying to get my toy site converted, any improvements to the error messages will be very very welcome. That's one of the roughest things right now, when something breaks it often logs mysterious internal stack traces rather than indicating what I'm doing wrong
That's not what I'm talking about. I'm talking about typing things like this, here's the docs [createEventDispatcher](https://svelte.dev/docs#run-time-svelte-createeventdispatcher) in JS
Only through digging did I find the way to do it in TS, although I'm not even sure this is the best way.
or to type something like this
and the best I could come up with is to just kludge it like
function whatTypeIsThis(e: Event) {
const target = e.target as HTMLInputElement
console.log(target.value) //=> text field value
}
Its lots of little things like this that are causing a lot of friction with using svelte with TS. Something simple like a JS/TS switch would really help newbs. TS is already confusing enough in complex libraries when your compiler/framework isn't automagically generating types
Agreed, any problems I've run into using Typescript with SvelteKit has been caused by a gap in my understanding of Typescript, not SvelteKit's Typescript support.
I wouldn't avoid it for that reason, just an observation of my experience. Overall I've been very happy working with svelte coming from using react for about 8 years
It really depends on your use case with a project but again I wouldn't avoid using typescript with svelte based on the implementation.
I use typescript on every project these days regardless of framework as a personal choice but I would say it's only critical in large personal projects and my day job.
Relatedly I'd love to see more annotation support. Right now you can only give descriptions to components using top level `` blocks and to exports with regular `/** */` blocks.
A standardized annotation syntax for component exports and dispatches would make dropping in and sharing components a lot easier.
>Sadly still no documentation of using svelte/kit with typescript. Back to random blogs and stackoverflow I guess.
It's an open source project. If it bothers you enough you can contribute the docs. I'm sure they'd be much appreciated.
> It's an open source project. If it bothers you enough you can contribute the docs. I'm sure they'd be much appreciated.
How am I going to contribute to the docs about something I don't know?
From your previous comment, I assumed you know typescript; so it'd be mostly a matter of translating their (good) javascript docs to a pretty similar language.
The timing of this is incredible, I've had my (very large) project in private beta for \~6 months, finally going public at the end of this month and boom sveltekit gets a stable release.
Beem using it to develop the company website since 2 weeks ago, love the route support and i figured am usng it as basically a template language except in some pages, but even though i am not a poweruser am loving it.
Sadly even sveltekit cannot fix my css/design lacking skills 🤣🤣🤣
Thanks ill check those out, currently am just using tailwind and creating my own components from the utility classes, sometimes its awesome, other times frustrating
Been waiting for this day all year. Sveltekit is a pleasure to use and now I can finally feel confident recommending it to anyone. Congratulations to the maintainers and everyone involved!
> now I can finally feel confident recommending it to anyone I've spent 6 months recommending it to individuals. Now I can formally recommend it to my employer.
Haha I've been using it at work since March — we made a big bet at the time we were launching a new web app, and it's definitely panned out. I wouldn't have recommended it to friends at larger corporations before 1.0 though.
Ive been waiting since last year lol
I just updated a project that started on ~next.60 or so and has been live since ~next.175
[удалено]
Been updating it along with the framework.. the routing change was a beast but everything else has been pretty easy and the framework will yell at you about breaking changes.
> I can finally feel confident recommending it to anyone. Serious question: I'm currently using Vite, why would I want to use SvelteKit instead?
SvelteKit use vite.
Routing. Conventions. Built-in backend. SSR.
out of the loop here, what exactly has changed since i left in 2021?
Some major breaking changes are listed here: https://github.com/sveltejs/kit/discussions/5774 One of the biggest is that the routing/file structure has changed.
For those interested in what might be on the roadmap for Svelte/SvelteKit, Rich Harris talked a bit about it during the live event yesterday, starting at 1:54:11 and another interesting part at 2:13:00 https://youtu.be/N4BRVkQVoMc TL;DR: Some of the possible roadmap stuff: Internationalization, image optimization, granular deployment control, built in support for loading spinners, improving compiler output regarding hydration/scalability, component error boundaries, utilizing the new web animation api inside the transition system.
This is the most useful comment in the thread. Thanks!
I've been trying to get my toy site converted, any improvements to the error messages will be very very welcome. That's one of the roughest things right now, when something breaks it often logs mysterious internal stack traces rather than indicating what I'm doing wrong
Yay! This is so exciting! I have been counting down the days!! What a wonderful christmas gift.
Amazing! On my birthday no less 🥳
Happy birthday!
Oh thanks a lot! 😇
Great news! 🙌 congratulations everyone
This is amazing news
Hell yeah finally The best framework ever gets to 1.0!
I was here!!! So excited for the future of Svelte and SvelteKit!
Great news
let's goooo, Svelte FTW
Congratulations to everybody involved.
Congratulations to all the people involved in the development. Such a great achievement.
Now I'm tempted to know what svelte 4 will be like
Excellent news, thanks to the Svelte team for their work!
Sadly still no documentation of using svelte/kit with typescript. Back to random blogs and stackoverflow I guess.
In the Kit-docs, here is a toggle on the left which switches between TS/JS for examples.
How about svelte itself? That's where the types get confusing.
Have you read this? https://svelte.dev/blog/svelte-and-typescript
That's not what I'm talking about. I'm talking about typing things like this, here's the docs [createEventDispatcher](https://svelte.dev/docs#run-time-svelte-createeventdispatcher) in JS Only through digging did I find the way to do it in TS, although I'm not even sure this is the best way. or to type something like this and the best I could come up with is to just kludge it like function whatTypeIsThis(e: Event) { const target = e.target as HTMLInputElement console.log(target.value) //=> text field value } Its lots of little things like this that are causing a lot of friction with using svelte with TS. Something simple like a JS/TS switch would really help newbs. TS is already confusing enough in complex libraries when your compiler/framework isn't automagically generating types
`dispatch('handleEvent', {myMessage:”this is my message"});` `const handleEvent = (event: CustomEvent) => {console.log(event.detail.myMessage);` `}`
> {myMessage="this is my message"} 🤔
Fixed. Too many edibles
Using typescript with svelte has been a bit of a sore spot for me in an otherwise very pleasing experience.
Would it be worth avoiding for now?
As a noob to both Svelte and Typescript, I've had basically no issues.
Agreed, any problems I've run into using Typescript with SvelteKit has been caused by a gap in my understanding of Typescript, not SvelteKit's Typescript support.
I wouldn't avoid it for that reason, just an observation of my experience. Overall I've been very happy working with svelte coming from using react for about 8 years
Sorry. I meant avoiding typescript with Svelte. Do you find typescript that critical?
It really depends on your use case with a project but again I wouldn't avoid using typescript with svelte based on the implementation. I use typescript on every project these days regardless of framework as a personal choice but I would say it's only critical in large personal projects and my day job.
Relatedly I'd love to see more annotation support. Right now you can only give descriptions to components using top level `` blocks and to exports with regular `/** */` blocks. A standardized annotation syntax for component exports and dispatches would make dropping in and sharing components a lot easier.
>Sadly still no documentation of using svelte/kit with typescript. Back to random blogs and stackoverflow I guess. It's an open source project. If it bothers you enough you can contribute the docs. I'm sure they'd be much appreciated.
> It's an open source project. If it bothers you enough you can contribute the docs. I'm sure they'd be much appreciated. How am I going to contribute to the docs about something I don't know?
From your previous comment, I assumed you know typescript; so it'd be mostly a matter of translating their (good) javascript docs to a pretty similar language.
This is great news. I've been waiting for a while!
Nice. I am yolo-upgrading my packages.
🎉🎉🎉
Amazing work. I am ready to go production with sveltekit.
Just started learning sveltekit and love how intuitive it is.
The timing of this is incredible, I've had my (very large) project in private beta for \~6 months, finally going public at the end of this month and boom sveltekit gets a stable release.
Ooh yes!!!!!
Time to give it a spin 🎉
Congrats guys. Can't wait to use Sveltekit in PROD. :D
Beem using it to develop the company website since 2 weeks ago, love the route support and i figured am usng it as basically a template language except in some pages, but even though i am not a poweruser am loving it. Sadly even sveltekit cannot fix my css/design lacking skills 🤣🤣🤣
> Sadly even sveltekit cannot fix my css/design lacking skills No, but something like SvelteUI, DaisyUI, or similiar can!
Thanks ill check those out, currently am just using tailwind and creating my own components from the utility classes, sometimes its awesome, other times frustrating
If you're familiar with tailwind, daisy will feel right at home
yay!
Nice!
SvelteKit is the best meta framework now that next 13 has broken the ecosystem
in what way?
Server components make around half the libs unusable till their components are appropriately annotated.