Static adapter deployment in Svelte - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ component_behavior

intermediate

What happens when you run npm run build with SvelteKit's static adapter?

Consider a SvelteKit project configured with the static adapter. You run npm run build. What is the expected output behavior?

A It produces a client-only SPA without any server-side rendering or pre-rendered pages.

B It creates a Node.js server bundle that serves pages dynamically at runtime.

C It generates a fully static site with pre-rendered HTML files for each route in the <code>build</code> directory.

D It outputs a Docker container image ready for deployment.

💡 Hint

Think about what a static adapter does compared to server adapters.

The static adapter pre-renders all pages at build time, producing static HTML files. This allows deployment to static hosts without a server.

📝 Syntax

intermediate

Which configuration snippet correctly sets up the static adapter in svelte.config.js?

Choose the correct way to import and configure the static adapter in svelte.config.js for SvelteKit.

A

import adapter from '@sveltejs/adapter-static';

export default {
  kit: {
    adapter: adapter()
  }
};

B

import staticAdapter from '@sveltejs/adapter-static';

export default {
  kit: {
    adapter: staticAdapter
  }
};

C

const adapter = require('@sveltejs/adapter-static');

export default {
  kit: {
    adapter: adapter()
  }
};

D

import adapter from '@sveltejs/adapter-static';

export default {
  kit: {
    adapter: adapter
  }
};

💡 Hint

Remember to call the adapter function when assigning it.

The static adapter must be imported and then called as a function to configure it properly.

🔧 Debug

advanced

Why does the static adapter fail to generate pages for dynamic routes without prerender.entries configured?

You have dynamic routes like [slug].svelte in your SvelteKit app. After building with the static adapter, those pages are missing. What is the cause?

A Dynamic routes are not supported at all by the static adapter and must be removed.

B The static adapter only pre-renders routes explicitly listed in <code>prerender.entries</code> or discovered via links; dynamic routes need manual entries.

C The static adapter requires a special plugin to handle dynamic routes automatically.

D Dynamic routes are pre-rendered by default without extra configuration.

💡 Hint

Think about how static generation discovers pages to build.

The static adapter pre-renders pages it can find by crawling links or explicit entries. Dynamic routes need to be listed in prerender.entries to generate their pages.

❓ state_output

advanced

What is the value of import.meta.env.SSR during static adapter build and runtime?

In a SvelteKit app using the static adapter, what does import.meta.env.SSR evaluate to during build and when running the static site in the browser?

A It is <code>true</code> during build (server-side rendering) and <code>false</code> in the browser at runtime.

B It is <code>false</code> during build and <code>true</code> in the browser.

C It is always <code>true</code> because the app is pre-rendered.

D It is always <code>false</code> because the static adapter disables SSR.

💡 Hint

Consider when SSR code runs and when client code runs.

import.meta.env.SSR is true during build because the app is rendered on the server. In the browser, it is false because the code runs client-side.

🧠 Conceptual

expert

Which deployment scenario best fits SvelteKit's static adapter?

Given these deployment environments, which one is the best fit for a SvelteKit app built with the static adapter?

A A serverless function platform that requires server-side rendering on each request.

B A Node.js server environment running the SvelteKit server for dynamic SSR.

C A Docker container running a custom Express server to serve SvelteKit pages dynamically.

D A CDN or static hosting service like Netlify, Vercel (static mode), or GitHub Pages serving pre-built HTML and assets.

💡 Hint

Think about what static adapter output is and where it can be hosted.

The static adapter produces static files that can be served by any static hosting or CDN without a server. Dynamic servers or serverless functions are not needed.