1. Does SvelteKit depend on Node.js? #

Node.js is required for development and building your SvelteKit app—you’ll need it to run the dev server (npm run dev) and compile your code into production-ready assets. However, it’s not always required for deployment.

The key here is SvelteKit’s adapter system:

• If you use adapter-static, it generates a fully static set of HTML/CSS/JS files (no server-side runtime needed). You can serve these with any web server, including your Go backend.
• Other adapters like adapter-node do require Node.js to run the app, but those are for cases where you need dynamic SSR or server-side logic. For your use case, adapter-static is the way to go.

2. Can I use the same Go + dist folder approach as Vue? #

Absolutely! Here’s how to replicate that workflow with SvelteKit:

1. Configure adapter-static in your svelte.config.js:

   import adapter from '@sveltejs/adapter-static';
   
   export default {
     kit: {
       adapter: adapter({
         pages: 'build', // Output directory for static files
         assets: 'build',
         fallback: null // Set to 'index.html' if you need client-side routing
       }),
       prerender: {
         entries: ['*'] // Prerender all routes as static HTML
       }
     }
   };
   

2. Run npm run build to generate your static assets in the build folder (or whatever directory you specified).
3. Embed this build directory into your Go binary using the embed package, just like you did with Vue’s dist folder. Example Go code:

   package main
   
   import (
     "embed"
     "net/http"
   )
   
   //go:embed all:build
   var staticAssets embed.FS
   
   func main() {
     // Serve the static files from the embedded directory
     http.Handle("/", http.FileServer(http.FS(staticAssets)))
     http.ListenAndServe(":8080", nil)
   }
   

4. Compile your Go app as usual—you’ll get a single executable that includes all your SvelteKit static assets.

3. Should I learn Svelte or SvelteKit? #

Since you’re building multi-page apps and already familiar with vanilla JS/Bootstrap, SvelteKit is almost certainly the better choice—even if SSR feels like a "nice-to-have" right now. Here’s why:

• Built-in routing: SvelteKit’s src/routes directory automatically maps to your app’s URL structure (no need to set up a third-party router like you might have with vanilla Svelte). This is a huge time-saver for multi-page apps.
• No Node runtime required for deployment: As we covered earlier, adapter-static lets you build static files that work with your Go backend—you don’t need to run Node.js in production.
• Minimal boilerplate: SvelteKit inherits Svelte’s vanilla-like syntax, which will feel familiar coming from Bootstrap + vanilla JS. It’s way less verbose than Vue, which you already tried and abandoned.
• Scalability: Even if you don’t need SSR now, SvelteKit makes it easy to add later (just switch adapters) if your app grows to need dynamic content. It also includes built-in features like code splitting, API route handling, and static site generation (SSG) out of the box.
• Official framework support: SvelteKit is the official recommended way to build Svelte apps for production, so you’ll get better documentation, community support, and long-term updates than using standalone Svelte for complex projects.

If you only needed to build isolated components or a tiny single-page app, standalone Svelte would suffice—but for multi-page apps with the workflow you’re using (Go + embedded static assets), SvelteKit is the more practical and future-proof choice.

内容的提问来源于stack exchange，提问作者xrfang