Nem acredito que eu ganhei um curso do trabalho que realmente vão me dar tempo pra fazer k k k
Cursinho de #svelte tô curtindo muito
"Svelte 5 marks a significant change in the language itself. "Runes" are a new way of writing reactive code with Svelte. This allows a major simplification of the API and surface area of Svelte, making Svelte easier for beginners to learn and use. I think it was a smart move, as it surely makes it easier for people to switch to Svelte."
„JavaScript framework reinvents itself… Did "runes" just ruin Svelte?“ https://www.youtube.com/watch?v=aYyZUDFZTrM
It might be time for my yearly "get really into #Svelte for some reason" episode. Is v6 coming out soon?
It's here! Svelte v5 was just released!!
https://github.com/sveltejs/svelte/releases/tag/svelte%405.0.0
Svelte 5 has been released:
https://github.com/sveltejs/svelte/releases/tag/svelte%405.0.0
Ich suche Hinweise, was für ein Format #Svelte in seinen __data.json Dateien (bzw Anfragen) verwendet oder fertige Parser dafür. Kennt da jemand was oder hat nützliche HInweise? Gerne RT.
Injee now supports pagination https://yu7.in/jqAcjZ
@idan this is really interesting.
I've been trying to move away from JS frontend frameworks because I find state management to be such a pain and the frameworks seem to get increasingly complicated, but maybe #Supabase makes that easier and thus justifies the use of #svelte or another frontend framework?
So, I’ve written something that is kind of like an ORM for #Supabase and #svelte.
But for many tables, some columns are only filled in when the row is written. Autoincrementing IDs, created_at timestamps, etc etc.
I'm not sure how I ought to handle this and keep everything typesafe. At creation time, I’m creating a record (object that looks like a row) but it's missing the autogenerated columns, which means my "optimistic" record is not a valid row record.
But I don't want to relax the type definition for a record since I want the record type to include those columns later on.
Not sure how other ORMs handle this situation.
Feeling a bit cruddy today so I'm taking it easy by converting my personal site from #Middleman to #SvelteKit, if only to see what's involved.
I want to keep out the Vite eco-system for my next project, so that eliminated my general fav #Svelte/#SvelteKit.
I had a go at Lit for web components, but Lit wasn't a good match for what I was building. It's not its "fault" per se -- I was asking too much and not aligning with the core spirit of web components.
I also wanted something that is generally #nobuild (which both #Preact and Lit can be).
Maybe I've made a dubious choice, but I need to make A choice.