Less Boilerplate, More Building: My Transition to SvelteKit

If you’ve been following my work on projects like FRCGames or Hermit, you know I’m a fan of moving fast. As a developer, there is nothing quite as soul-crushing as spending three hours configuring a router or fighting with state management before you’ve even written a single line of your actual application logic.

For a long time, I operated within the "industry standard" ecosystems. But recently, I made a definitive shift. I’m trading in the heavy lifting for something leaner. Here is why I’m moving my primary development focus to SvelteKit.

In modern web development, we often pay what I call a "boilerplate tax." Whether it’s React’s useEffect hooks or the complex setup required for some Next.js configurations, you’re often writing code for the framework rather than for the user.

SvelteKit flips this script. Because Svelte is a compiler rather than a library, it understands what you’re trying to do at build time.

Why SvelteKit Wins for Me:

• True Reactivity: No more useState. If I want to update a variable, I just assign it: count += 1. The framework handles the rest.
• Filesystem Routing: It’s intuitive. Building out the directory for FOSS Dump felt natural—if I wanted a new page, I just made a new folder with a +page.svelte.
• Server-Side First: The way SvelteKit handles load functions makes fetching data from APIs (like The Blue Alliance for my FRC projects) feel like a native part of the language rather than an afterthought.

From Concept to Public Beta

When I launched FRCGames in public beta, the goal was simple: creating a fast, competitive space for the robotics community to engage with scouting data and game strategy. When you’re building for a community that thrives on precision and real-time stats, the technical stack needs to be invisible so the data can shine.

SvelteKit allowed me to focus on the logic of the guessing games and the seamless integration of The Blue Alliance API, rather than fighting with complex state management or re-rendering lags. This efficiency is exactly what allowed me to scale the site’s features quickly without getting bogged down in configuration. When the boilerplate disappears, I can spend more time building tools for teams and less time debugging the framework.

The FOSS Philosophy

As an advocate for Free and Open Source Software (FOSS), I appreciate tools that lower the barrier to entry. SvelteKit’s documentation is some of the best in the business, making it easier for contributors to jump into my projects like FOSS Dump without needing a PhD in framework-specific quirks.

What’s Next?

I’m currently rebuilding the foundation of my projects using this stack. The speed of SvelteKit combined with the power of Supabase has become my "killer combo" for 2026.

If you’re tired of fighting your tools and just want to get back to building cool stuff, give SvelteKit a shot. You might find that the best code is the code you didn't have to write.