home.social

#sveltekit — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #sveltekit, aggregated by home.social.

  1. Been playing with #SvelteKit, #KonstaUI, #Drizzle, #betterauth, #superforms, and #zog. Don't hate it so far, despite the classical frustration of "I could do this in seconds in #Angular, but I need to spend 5 minutes looking it up" that always happens when you start working with something new.

    Got the skeleton of the app set up, CI/CD running, database connection (including migrations), and authentication. Just need to get the user registration set up, and then I can start with the actual content.
  2. Been playing with #SvelteKit, #KonstaUI, #Drizzle, #betterauth, #superforms, and #zog. Don't hate it so far, despite the classical frustration of "I could do this in seconds in #Angular, but I need to spend 5 minutes looking it up" that always happens when you start working with something new.

    Got the skeleton of the app set up, CI/CD running, database connection (including migrations), and authentication. Just need to get the user registration set up, and then I can start with the actual content.
  3. Been playing with #SvelteKit, #KonstaUI, #Drizzle, #betterauth, #superforms, and #zog. Don't hate it so far, despite the classical frustration of "I could do this in seconds in #Angular, but I need to spend 5 minutes looking it up" that always happens when you start working with something new.

    Got the skeleton of the app set up, CI/CD running, database connection (including migrations), and authentication. Just need to get the user registration set up, and then I can start with the actual content.
  4. Gestern Nacht habe ich ein großes TransDB Update ausgerollt.

    Die 4 jahre alte SvelteKit Beta wurde auf die neuste Svelte 5 + SvelteKit Version geupdated.
    Aufgrund der ganzen breaking changes über die Jahre musste im Grunde das gesamte Projekt vollständig migriert werden.

    Falls euch Fehler in der Seite auffallen, gerne bei mir melden.

    #transdb #svelte #sveltekit

  5. Gestern Nacht habe ich ein großes TransDB Update ausgerollt.

    Die 4 jahre alte SvelteKit Beta wurde auf die neuste Svelte 5 + SvelteKit Version geupdated.
    Aufgrund der ganzen breaking changes über die Jahre musste im Grunde das gesamte Projekt vollständig migriert werden.

    Falls euch Fehler in der Seite auffallen, gerne bei mir melden.

    #transdb #svelte #sveltekit

  6. Gestern Nacht habe ich ein großes TransDB Update ausgerollt.

    Die 4 jahre alte SvelteKit Beta wurde auf die neuste Svelte 5 + SvelteKit Version geupdated.
    Aufgrund der ganzen breaking changes über die Jahre musste im Grunde das gesamte Projekt vollständig migriert werden.

    Falls euch Fehler in der Seite auffallen, gerne bei mir melden.

    #transdb #svelte #sveltekit

  7. Gestern Nacht habe ich ein großes TransDB Update ausgerollt.

    Die 4 jahre alte SvelteKit Beta wurde auf die neuste Svelte 5 + SvelteKit Version geupdated.
    Aufgrund der ganzen breaking changes über die Jahre musste im Grunde das gesamte Projekt vollständig migriert werden.

    Falls euch Fehler in der Seite auffallen, gerne bei mir melden.

    #transdb #svelte #sveltekit

  8. Gestern Nacht habe ich ein großes TransDB Update ausgerollt.

    Die 4 jahre alte SvelteKit Beta wurde auf die neuste Svelte 5 + SvelteKit Version geupdated.
    Aufgrund der ganzen breaking changes über die Jahre musste im Grunde das gesamte Projekt vollständig migriert werden.

    Falls euch Fehler in der Seite auffallen, gerne bei mir melden.

    #transdb #svelte #sveltekit

  9. As an excercise, made #opencode slop together a basic #SvelteKit frontend (and #golang middleware) for miniflux.

    Lost interest as soon as it got to somewhat usable state. Wondering if it's a me problem.

    Annoyed that I haven't learnt anything through this experience. Delighted by how base scaffolding kinda just appeared.

    Terrified by a thought that eventually we (the people) will start talking to each other the way we have to talk to LLMs.

    At least I gave it a cool name, huh?

  10. As an excercise, made #opencode slop together a basic #SvelteKit frontend (and #golang middleware) for miniflux.

    Lost interest as soon as it got to somewhat usable state. Wondering if it's a me problem.

    Annoyed that I haven't learnt anything through this experience. Delighted by how base scaffolding kinda just appeared.

    Terrified by a thought that eventually we (the people) will start talking to each other the way we have to talk to LLMs.

    At least I gave it a cool name, huh?

  11. As an excercise, made #opencode slop together a basic #SvelteKit frontend (and #golang middleware) for miniflux.

    Lost interest as soon as it got to somewhat usable state. Wondering if it's a me problem.

    Annoyed that I haven't learnt anything through this experience. Delighted by how base scaffolding kinda just appeared.

    Terrified by a thought that eventually we (the people) will start talking to each other the way we have to talk to LLMs.

    At least I gave it a cool name, huh?

  12. As an excercise, made #opencode slop together a basic #SvelteKit frontend (and #golang middleware) for miniflux.

    Lost interest as soon as it got to somewhat usable state. Wondering if it's a me problem.

    Annoyed that I haven't learnt anything through this experience. Delighted by how base scaffolding kinda just appeared.

    Terrified by a thought that eventually we (the people) will start talking to each other the way we have to talk to LLMs.

    At least I gave it a cool name, huh?

  13. As an excercise, made #opencode slop together a basic #SvelteKit frontend (and #golang middleware) for miniflux.

    Lost interest as soon as it got to somewhat usable state. Wondering if it's a me problem.

    Annoyed that I haven't learnt anything through this experience. Delighted by how base scaffolding kinda just appeared.

    Terrified by a thought that eventually we (the people) will start talking to each other the way we have to talk to LLMs.

    At least I gave it a cool name, huh?

  14. I played around with the new (experimental) `query.live()` remote functions in #sveltekit. Used #wienerlinien public transit depatures from their real-time endpoints –`query.live` is a really good fit for something like this (pulling the data every 15 seconds and updating the UI accordingly).
    I feel the docs could be clearer on how the transport actually works. It's neither server-sent event, nor websockets – it's regular GETs with chunked responses!
    svelte.dev/docs/kit/remote-fun

  15. I played around with the new (experimental) `query.live()` remote functions in #sveltekit. Used #wienerlinien public transit depatures from their real-time endpoints –`query.live` is a really good fit for something like this (pulling the data every 15 seconds and updating the UI accordingly).
    I feel the docs could be clearer on how the transport actually works. It's neither server-sent event, nor websockets – it's regular GETs with chunked responses!
    svelte.dev/docs/kit/remote-fun

  16. I played around with the new (experimental) `query.live()` remote functions in #sveltekit. Used #wienerlinien public transit depatures from their real-time endpoints –`query.live` is a really good fit for something like this (pulling the data every 15 seconds and updating the UI accordingly).
    I feel the docs could be clearer on how the transport actually works. It's neither server-sent event, nor websockets – it's regular GETs with chunked responses!
    svelte.dev/docs/kit/remote-fun

  17. I played around with the new (experimental) `query.live()` remote functions in #sveltekit. Used #wienerlinien public transit depatures from their real-time endpoints –`query.live` is a really good fit for something like this (pulling the data every 15 seconds and updating the UI accordingly).
    I feel the docs could be clearer on how the transport actually works. It's neither server-sent event, nor websockets – it's regular GETs with chunked responses!
    svelte.dev/docs/kit/remote-fun

  18. I played around with the new (experimental) `query.live()` remote functions in #sveltekit. Used #wienerlinien public transit depatures from their real-time endpoints –`query.live` is a really good fit for something like this (pulling the data every 15 seconds and updating the UI accordingly).
    I feel the docs could be clearer on how the transport actually works. It's neither server-sent event, nor websockets – it's regular GETs with chunked responses!
    svelte.dev/docs/kit/remote-fun

  19. As much as I like to do everything myself, I chose to use an off-the-shelf #Markdown parser for my personal site.

    There may sometimes be a good reason to re-invent the wheel — even if it is just to learn more about wheels — but using an established tool or package can save you time and headaches. However, the key is to know which to use and when.

    carledwardlyons.ca/articles/de

    #markdownit #svelte #sveltekit #HTML #CSS #typescript #javascript #webdesign #webdev #software #devlog #blog

  20. As much as I like to do everything myself, I chose to use an off-the-shelf #Markdown parser for my personal site.

    There may sometimes be a good reason to re-invent the wheel — even if it is just to learn more about wheels — but using an established tool or package can save you time and headaches. However, the key is to know which to use and when.

    carledwardlyons.ca/articles/de

    #markdownit #svelte #sveltekit #HTML #CSS #typescript #javascript #webdesign #webdev #software #devlog #blog

  21. As much as I like to do everything myself, I chose to use an off-the-shelf #Markdown parser for my personal site.

    There may sometimes be a good reason to re-invent the wheel — even if it is just to learn more about wheels — but using an established tool or package can save you time and headaches. However, the key is to know which to use and when.

    carledwardlyons.ca/articles/de

    #markdownit #svelte #sveltekit #HTML #CSS #typescript #javascript #webdesign #webdev #software #devlog #blog

  22. As much as I like to do everything myself, I chose to use an off-the-shelf #Markdown parser for my personal site.

    There may sometimes be a good reason to re-invent the wheel — even if it is just to learn more about wheels — but using an established tool or package can save you time and headaches. However, the key is to know which to use and when.

    carledwardlyons.ca/articles/de

    #markdownit #svelte #sveltekit #HTML #CSS #typescript #javascript #webdesign #webdev #software #devlog #blog

  23. As much as I like to do everything myself, I chose to use an off-the-shelf parser for my personal site.

    There may sometimes be a good reason to re-invent the wheel — even if it is just to learn more about wheels — but using an established tool or package can save you time and headaches. However, the key is to know which to use and when.

    carledwardlyons.ca/articles/de

  24. I could have hard-coded all the text, styles, and other data into my personal website. However, that would have been too easy.

    I decided to make my entire #webapp#blog and all — into a #template populated by #JSON and #Markdown. This was mostly just an exercise in #design, but I also wanted to make it something i could #opensource.

    carledwardlyons.ca/articles/de

    #svelte #sveltekit #typescript #javascript #webdesign #software #blog #devlog

  25. I could have hard-coded all the text, styles, and other data into my personal website. However, that would have been too easy.

    I decided to make my entire #webapp#blog and all — into a #template populated by #JSON and #Markdown. This was mostly just an exercise in #design, but I also wanted to make it something i could #opensource.

    carledwardlyons.ca/articles/de

    #svelte #sveltekit #typescript #javascript #webdesign #software #blog #devlog

  26. I could have hard-coded all the text, styles, and other data into my personal website. However, that would have been too easy.

    I decided to make my entire #webapp#blog and all — into a #template populated by #JSON and #Markdown. This was mostly just an exercise in #design, but I also wanted to make it something i could #opensource.

    carledwardlyons.ca/articles/de

    #svelte #sveltekit #typescript #javascript #webdesign #software #blog #devlog

  27. I could have hard-coded all the text, styles, and other data into my personal website. However, that would have been too easy.

    I decided to make my entire #webapp#blog and all — into a #template populated by #JSON and #Markdown. This was mostly just an exercise in #design, but I also wanted to make it something i could #opensource.

    carledwardlyons.ca/articles/de

    #svelte #sveltekit #typescript #javascript #webdesign #software #blog #devlog

  28. I could have hard-coded all the text, styles, and other data into my personal website. However, that would have been too easy.

    I decided to make my entire and all — into a populated by and . This was mostly just an exercise in , but I also wanted to make it something i could .

    carledwardlyons.ca/articles/de

  29. I was reading the #sveltekit docs, apparently the definition of a “pure function” is vastly different in the #javascript world. In their “pure” functions, you can still query a third-party API. 🤦‍♂️ 🤦‍♂️

  30. I was reading the #sveltekit docs, apparently the definition of a “pure function” is vastly different in the #javascript world. In their “pure” functions, you can still query a third-party API. 🤦‍♂️ 🤦‍♂️

  31. I was reading the #sveltekit docs, apparently the definition of a “pure function” is vastly different in the #javascript world. In their “pure” functions, you can still query a third-party API. 🤦‍♂️ 🤦‍♂️

  32. I was reading the #sveltekit docs, apparently the definition of a “pure function” is vastly different in the #javascript world. In their “pure” functions, you can still query a third-party API. 🤦‍♂️ 🤦‍♂️

  33. I was reading the #sveltekit docs, apparently the definition of a “pure function” is vastly different in the #javascript world. In their “pure” functions, you can still query a third-party API. 🤦‍♂️ 🤦‍♂️

  34. #Gatsby starters and plugins (some starters use Axios for data fetching)
    #SvelteKit example projects (can be configured to use Axios)
    #Tauri apps (examples showing Axios with custom fetch adapter)
    #Nodejs backend utilities and CLI tools (server-side HTTP requests with Axios)

  35. starters and plugins (some starters use Axios for data fetching)
    example projects (can be configured to use Axios)
    apps (examples showing Axios with custom fetch adapter)
    backend utilities and CLI tools (server-side HTTP requests with Axios)

  36. #Gatsby starters and plugins (some starters use Axios for data fetching)
    #SvelteKit example projects (can be configured to use Axios)
    #Tauri apps (examples showing Axios with custom fetch adapter)
    #Nodejs backend utilities and CLI tools (server-side HTTP requests with Axios)

  37. EvaTeam Workflow Enhancer — userscript для нормального отображения процессов

    Сталкивались уже с EvaTeam (российский аналог Jira)? Чувствуете боль при работе с бизнес-процессами (workflow)? Думаю я могу вам немного помочь

    habr.com/ru/articles/1015656/

    #userscript #userscripts #tampermonkey #greasemonkey #eva #evateam #workflow #svelte #sveltejs #sveltekit