home.social

#sveltekit — Public Fediverse posts

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

  1. بسام.سوشيال: منصة تواصل اجتماعي لامركزي مبنية على HybridSocial وبروتوكول ActivityPub

    بسام.سوشيال هي منصة تواصل اجتماعي عربية لامركزية، مبنية على البرمجية مفتوحة المصدر HybridSocial، والتي تعتمد بدورها على بروتوكول ActivityPub القياسي. تقدم المنصة ميزات متقدمة مثل التفاعلات السبعة، والمجموعات، والفيديو...

    🔗 https://salehgnutux.github.io/GT-NEWSTECH/ar/foss/bassam-social-hybridsocial-activitypub/

    #بسام #HybridSocial #ActivityPub #لامركزي #فيديفرس #Elixir #Phoenix #SvelteKit #gnutux

  2. It's quite interesting how one would build online maps with an "add place" form for hobby projects nowadays. Like makevienna.cool/ or pingpongmap.net/.

    One way is a shared PHP Webspace, small SQL database and maybe a tiny API framework like #slimphp or #leafphp (abandonded?) on top. Caching via stored JSON file of POIs.

    Another way I'd like to try could be with #SvelteKit #Svelte remote functions, e.g. on #Cloudflare. svelte.dev/docs/kit/remote-fun
    A Cloudflare D1 (?) SQL database would be needed here as well.

    Would like to try it just for fun, might be a simple stack for hobby projects with user input?

    How would you build a map like this? 👨‍🔧 #WebDev

  3. It's quite interesting how one would build online maps with an "add place" form for hobby projects nowadays. Like makevienna.cool/ or pingpongmap.net/.

    One way is a shared PHP Webspace, small SQL database and maybe a tiny API framework like #slimphp or #leafphp (abandonded?) on top. Caching via stored JSON file of POIs.

    Another way I'd like to try could be with #SvelteKit #Svelte remote functions, e.g. on #Cloudflare. svelte.dev/docs/kit/remote-fun
    A Cloudflare D1 (?) SQL database would be needed here as well.

    Would like to try it just for fun, might be a simple stack for hobby projects with user input?

    How would you build a map like this? 👨‍🔧 #WebDev

  4. It's quite interesting how one would build online maps with an "add place" form for hobby projects nowadays. Like makevienna.cool/ or pingpongmap.net/.

    One way is a shared PHP Webspace, small SQL database and maybe a tiny API framework like #slimphp or #leafphp (abandonded?) on top. Caching via stored JSON file of POIs.

    Another way I'd like to try could be with #SvelteKit #Svelte remote functions, e.g. on #Cloudflare. svelte.dev/docs/kit/remote-fun
    A Cloudflare D1 (?) SQL database would be needed here as well.

    Would like to try it just for fun, might be a simple stack for hobby projects with user input?

    How would you build a map like this? 👨‍🔧 #WebDev

  5. It's quite interesting how one would build online maps with an "add place" form for hobby projects nowadays. Like makevienna.cool/ or pingpongmap.net/.

    One way is a shared PHP Webspace, small SQL database and maybe a tiny API framework like #slimphp or #leafphp (abandonded?) on top. Caching via stored JSON file of POIs.

    Another way I'd like to try could be with #SvelteKit #Svelte remote functions, e.g. on #Cloudflare. svelte.dev/docs/kit/remote-fun
    A Cloudflare D1 (?) SQL database would be needed here as well.

    Would like to try it just for fun, might be a simple stack for hobby projects with user input?

    How would you build a map like this? 👨‍🔧 #WebDev

  6. It's quite interesting how one would build online maps with an "add place" form for hobby projects nowadays. Like makevienna.cool/ or pingpongmap.net/.

    One way is a shared PHP Webspace, small SQL database and maybe a tiny API framework like #slimphp or #leafphp (abandonded?) on top. Caching via stored JSON file of POIs.

    Another way I'd like to try could be with #SvelteKit #Svelte remote functions, e.g. on #Cloudflare. svelte.dev/docs/kit/remote-fun
    A Cloudflare D1 (?) SQL database would be needed here as well.

    Would like to try it just for fun, might be a simple stack for hobby projects with user input?

    How would you build a map like this? 👨‍🔧 #WebDev

  7. Oh, cool – #SvelteKit `query.live()` remote functions now use SSE (Server Sent Events) instead of streamed responses. github.com/sveltejs/kit/pull/1

  8. Oh, cool – #SvelteKit `query.live()` remote functions now use SSE (Server Sent Events) instead of streamed responses. github.com/sveltejs/kit/pull/1

  9. Oh, cool – #SvelteKit `query.live()` remote functions now use SSE (Server Sent Events) instead of streamed responses. github.com/sveltejs/kit/pull/1

  10. Oh, cool – #SvelteKit `query.live()` remote functions now use SSE (Server Sent Events) instead of streamed responses. github.com/sveltejs/kit/pull/1

  11. 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.
  12. 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.
  13. 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.
  14. 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

  15. 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

  16. 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

  17. 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

  18. 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

  19. 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?

  20. 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?

  21. 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?

  22. 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?

  23. 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?

  24. 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

  25. 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

  26. 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

  27. 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

  28. 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

  29. 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

  30. 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

  31. 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

  32. 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

  33. 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

  34. 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

  35. 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

  36. 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

  37. 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