[deleted]
SvelteKit 1.0
101–110 of 296 posts
Re: SvelteKit 1.0
#102There is so much "let me just see if this works..." tap tapppy tap .... "no... NO WAY... OMG IT WORKED!" with Svelte. Very little surface area. It embraces your knowledge of plain ole CSS/JS/HTML and empowers you with reactivity and a means of if being able to add motion to your ui. Newbs and Pros alike can build fast with it. That speed + reactivity allows your software to better keep up with your converstaions that…
Except it forces you to use node js, or do I read it wrong? Can we get a streamlined js framework that is just about the frontend and let’s you use whatever backend language you want? I know there is react, vue and angular but they seem so bloated
Nodejs is only needed in the development phase.
Re: SvelteKit 1.0
#103Congratulations to the team for releasing this. For someone who hasn't followed svelte closely, How much JS sveltekit ship by default using SSR
its up to you - you can ship 0 kb of js if you want by turning off client side rendering https://kit.svelte.dev/docs/page-options#csr and you have this choice on a per page basis rather than having to choose between a static site generator or a full SPA
0kb is best size of JS. Curious if I do want JS, how much is extra framework overhead
Re: SvelteKit 1.0
#104This is how I move fast and break nothing. By having fullstack type-safety from database all the way to the frontend with auto-completion. My current stack: + SvelteKit (could be Next, Nuxt, Solid or any other TypeScript framework) + tRPC (typed calls between frontend and backend, https://trpc.io ) + trpc-sveltekit (glues SvelteKit and tRPC, https://github.com/icflorescu/trpc-sveltekit ) + Prisma (ORM, https://www.pr…
Curious how you handle `request.formData()` in Form Actions and ensuring type safety there.
> Curious how you handle `request.formData()` in Form Actions and ensuring type safety there.
Hopefully the same way typed programming languages do it: parsing and type checking.
Re: SvelteKit 1.0
#105Earlier quoted context omitted.
You can start here: https://learn.svelte.dev/tutorial/welcome-to-svelte
> Yikes! We couldn't start the app. Please ensure third party cookies are enabled for this site. Yikes! No thanks.
You can also just install the demo package and play around with it on your own computer.
Re: SvelteKit 1.0
#106After a few minor versions, I hope they don't start to deprecate the newly added features.
Re: SvelteKit 1.0
#107This is how I move fast and break nothing. By having fullstack type-safety from database all the way to the frontend with auto-completion. My current stack: + SvelteKit (could be Next, Nuxt, Solid or any other TypeScript framework) + tRPC (typed calls between frontend and backend, https://trpc.io ) + trpc-sveltekit (glues SvelteKit and tRPC, https://github.com/icflorescu/trpc-sveltekit ) + Prisma (ORM, https://www.pr…
> This is how I move fast and break nothing
Absolutely impressive how you are one of the first to find a approach that leads to a 100% bug-free development methodology.
Or, you still have bugs right, so sometimes things break? Maybe you meant something like: This is how I move fast and don't have a certain section of bugs anymore?
Re: SvelteKit 1.0
#108Earlier quoted context omitted.
> It embraces your knowledge of plain ole CSS/JS/HTML Yeah that's one of the things I love about Svelte. It tends to enhance fundamental web knowledge rather than forcing you to think in convoluted ways. Features like actions put you close to the bare metal so to speak. I use those all the time.
This is what they said about React when it first blew up. Compared to Angular, it's much closer to being *just javascript™*. But I wonder how well that'll hold up after the honeymoon phase The builder.io team made a tool called Mitosis[^0] that lets you input a component written in almost any framework and automatically recreate that same component in any other framework including Vue, React, Qwik, Angular, Svelte, R…
I've been using Svelte for three years now, or close enough. The honeymoon phase hasn't waned.
Re: SvelteKit 1.0
#109Earlier quoted context omitted.
> you still have to rely on third party library for routing, state management, querying etc. Take a peek at Joystick [1]. I designed it as the exact antithesis to this. It's full-stack (Node.js back-end with a fully ssr'd component framework designed for the long-term) and doesn't introduce any special paradigms (i.e., vanilla HTML, CSS, and JavaScript—no attribute tricks/compilers needed). Everything is designed to…
Will take a look at it, and good luck with building it, such projects requires effort and test of time
Thank you, appreciate that. If you have any questions feel free to contact me directly: ryan.glover@cheatcode.co.
Re: SvelteKit 1.0
#110Exciting to see this hit 1.0! The new tutorial site looks great and I love that the sidebar is searchable now. Also the Cmd-K search on the docs (https://kit.svelte.dev/) is awesome to have as well.
I've been really enjoying working with Svelte for the last year or so now. My main project is a video editor, running under Tauri and using plain client-side Svelte, but I've also used SvelteKit to throw together a few little admin dashboard-y things and it's been very quick to get started with. Right now those projects are pretty lightweight too, just SvelteKit with TypeScript, the pg-promise package to connect with Postgres, and a handful of handwritten SQL queries.
Congrats to the team! Looking forward to see what the future holds for Svelte[Kit].