Use vite-node to access $lib in your #sveltekit app scripts!
https://github.com/sveltejs/kit/discussions/9807#discussioncomment-5792202
Introducing Orbit: A Revolutionary Tool for Streamlined Security Scanning
Orbit Scanner is set to transform the landscape of security assessments with its powerful integration of modern technologies. Designed for efficiency, it combines a sleek SvelteKit frontend with a rob...
Process and optimize external images in #SvelteKit - is it correct, that there is not yet an built-in alternative to Next Image or Nuxt Image? Nuxt Image uses IPX as built-in and self hosted image optimizer, no external CDNs ($) required. Thx for infos!
What’s the benefit of using #Deno for #SvelteKit, rather than Node? I do use TypeScript, but that’s never been something I had to setup myself or worry about. Vite just takes care of everything, and it’s all part of the project template created by SK.
I don’t really understand what a switch to Deno would give me? 
New #SvelteKit article: "Refactoring Svelte stores to $state runes".
Harnessing the Power of SvelteKit: A Dive into Dynamic Web Development
Discover the seamless integration of SvelteKit, Tailwind, and Firebase in creating an engaging static site. Experience the thrill of reactivity and user-friendly design, all while participating in a f...
https://news.lavx.hu/article/harnessing-the-power-of-sveltekit-a-dive-into-dynamic-web-development
I'm very busy migrating a big #SvelteKit project to #Svelte 5's new runes syntax and I have to be honest... not a big fan of the increased number of lines, especially when it comes to the props.
For example, what used to be a single line:
```
export let user: User | undefined = undefined;
```
Now takes 5 lines because of the added effort to properly type everything:
```
interface Props {
user?: User;
}
let { user }: Props = $props();
```
And yeah of course in this simple case I could do the type inline, but that doesn't scale when you have multiple props.
Really not of fan of this boilerplate.
A beautiful thing about the #Fediverse is that you can interact with it however you want. If you want a dark interface with flashes of red, goldenrod, and blue - no one is going to stop you. And you want to do it all with #WASM in your browser? That's fine. And you want #E2EE? Go for it. You want to do it with #SvelteKit and #RustLang? Fine. Whatever.
None of it is a trivial undertaking, of course. Although if you just want to interact with #ActivityPub from a database (or JSON files) and curl, you could build something over a weekend (see my older #SofaPub code for an example).
Threads and Bluesky really hold no interest for me. I exist on Threads solely so that I can be there in there event they actually do something interesting with ActivityPub integration (they're pretty damn slow about it, though). Until I can tell my non-technical friends on Threads to follow me here on #Enigmatick and they don't have to jump through a bunch of hoops, I'm skeptical. Bluesky… meh.
Question for the #svelte community here:
When you build a new application with #sveltekit, where do put your data layer and business logic?
Please reply with your custom solution if you choose the "something else" option.
I wanted to try to publish a #SvelteKit project to #Vercel, which is supposed to have first-class support. So I created a brand new SvelteKit project (`pnpx sv create myapp`) and then ran `pnpx vercel`, and I get a build failure.
Not a great start 
Thanks to @robin_maki, #SvelteKit integration support has been added to #Fedify! This feature will be included in Fedify 1.3.0.
Boom 
!
This is a game changer 
.
If you need to build your portfolio/blog/personal website using Markdown, take a look at this:
https://dev.to/robertobutti/how-to-build-a-content-driven-static-site-with-markdown-sveltekit-and-fusionable-347f
In the article, I used SvelteKit, but you can use Fusionable with all the JS frontend frameworks.
Neohtop — это Htop на стероидах
Приложение позволяет мониторить процессы в реальном времени, отслеживать использование CPU и памяти, а также обладает современным интерфейсом с темным и светлым режимами.
Пользователи могут искать процессы по различным критериям, фиксировать важные процессы и управлять ими, включая завершение.
Статистика системы обновляется автоматически, а сортировка доступна по любому столбцу.
Для разработки используется SvelteKit и TypeScript на фронтенде, Rust и Tauri на бэкенде, а также CSS Variables для стилизации и FontAwesome для иконок.
#NeoHtop: Cross-platform system monitor combining #Svelte, #Rust, and #Tauri for a modern monitoring experience #opensource
Key features:
Real-time process monitoring
CPU & memory usage tracking
Process search & filtering
Dark/light theme support
Tech stack:
Frontend: #SvelteKit, #TypeScript
Backend: #Rust, #Tauri
Styling: CSS Variables
Development requirements:
#NodeJS (v16+)
Latest stable #Rust
Xcode Command Line Tools (for #macOS)
Learn more: https://github.com/Abdenasser/neohtop
So, been working with #svelte & #sveltekit for the past couple weeks, but have run into what I think is a conceptual problem.. It has to do with creating a Component with a store that might be used multiple times (with a different store value) meaning that I'm trying to achieve a 'reactive contextual store'. I've gone through all the online guides/vids I can find, but can't find a working solution. Note that I'm *not* using TypeScript. Anyone out there able to offer a bit of targeted #FediHelp?
I am once again asking if anyone is interested in helping me work on a tool for sorting, hosting, and sharing images and eventually videos (hopefully). This will be great for artists, yuri collectors, sorting memes, and more
Are you a frontend dev? A backend dev? We need both. If you know HTML, svelte, typescript, or nestjs these are some of the things we are using.
Perhaps ur none of that and just want to stay up to date with the progress, give feedback, or help translate the tool. Well then feel free to join the discord or follow me here since ill post my progress.
Discord: https://discord.gg/tcXrRWccU5
Matrix: #artist-image-tool-dev:platypus-sandbox.com
Also id like to have someone review some of my open PR's cuz at some point I'm just gonna have to force push or the whole project stalls. Also it would be more fun if this didn't more of less become a solo project
Oh also have some of the lastest WIP images of the project:
#FOSS #svelte #SvelteKit #software #frontend #backend #backenddeveloper #FLOSS #typescript #SelfHosted
Hey everyone! Episode 75 of ‘This Week in Svelte’ is out, and @paoloricciuti is covering the latest changelog, the downsides of $prop and why maintainers went with $props, and a brief demonstration of why sometimes you don’t need $state.
Definitely worth a watch 
https://www.youtube.com/watch?v=bFodoz9Mlbw
