Static adapter deployment in Svelte - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of the static adapter in SvelteKit?

The static adapter generates a fully static version of your SvelteKit app. It pre-renders pages as HTML files so you can deploy your site to any static hosting service without a server.

beginner

How do you configure the static adapter in a SvelteKit project?

You install the adapter with npm and then import it in your svelte.config.js file. Inside the config, you set the adapter to the static adapter, like this: <br><code>import adapter from '@sveltejs/adapter-static';<br>export default { kit: { adapter: adapter() } };</code>

intermediate

What is prerendering in the context of static adapter deployment?

Prerendering means generating HTML pages at build time instead of on the server at runtime. The static adapter prerenders pages so they can be served as simple HTML files, improving speed and allowing static hosting.

beginner

Which folder contains the generated static files after building with the static adapter?

The static files are generated in the build folder by default. This folder contains all the HTML, CSS, JS, and assets ready to be uploaded to a static host.

intermediate

Can you use dynamic server-side features with the static adapter?

No, the static adapter only supports static content. Features that require a server, like server-side API routes or dynamic rendering, won't work because the site is fully static.

What does the static adapter in SvelteKit produce?

A A serverless function bundle

B A fully static site with pre-rendered HTML files

C A client-only single page app

D A Node.js server for dynamic rendering

The static adapter generates a fully static site by pre-rendering pages as HTML files.

Where do you specify the static adapter in a SvelteKit project?

A In svelte.config.js under kit.adapter

B In package.json scripts

C In the main.js entry file

D In the index.html file

The adapter is configured in svelte.config.js inside the kit.adapter property.

Which command builds a static site using the static adapter?

A npm run dev

B npm run static

C npm start

D npm run build

The build command generates the static files using the configured adapter.

What happens if your app uses server-side API routes with the static adapter?

A They are converted to client-side fetch calls

B They run as serverless functions automatically

C They will not work because the site is fully static

D They are ignored but do not cause errors

Server-side API routes require a server and won't work with a fully static site.

Which folder contains the static site output after building?

A build

B src

C public

D node_modules

The build folder contains the generated static files ready for deployment.

Explain how the static adapter changes the way a SvelteKit app is deployed and what benefits it offers.

Think about what happens at build time and how the site runs after deployment.

Describe the steps to set up and build a SvelteKit project using the static adapter.

Focus on configuration and commands.

Practice

1. What is the main purpose of the static adapter in a SvelteKit project?

easy

A. To add real-time communication features

B. To enable server-side rendering with dynamic data

C. To connect the app to a database automatically

D. To generate static files for hosting without a backend server

Solution

1. Step 1: Understand what static adapter does

   The static adapter converts your SvelteKit app into static files like HTML, CSS, and JS.

2. Step 2: Identify the hosting benefit

   These static files can be hosted easily on any static hosting service without needing a backend server.

3. Final Answer:

   To generate static files for hosting without a backend server -> Option D

4. Quick Check:

   Static adapter = static files for hosting [OK]

Hint: Static adapter means no backend, just static files [OK]

Common Mistakes:

• Confusing static adapter with server-side rendering
• Thinking it connects to databases
• Assuming it adds dynamic real-time features

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

easy

A. export default {
kit: {
adapter: '@sveltejs/adapter-static'
}
};

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

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

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

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

D. import adapter from '@sveltejs/adapter-node';

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

Solution

1. Step 1: Check import statement

   The static adapter must be imported from '@sveltejs/adapter-static' and assigned to a variable.

2. Step 2: Confirm adapter usage

   The adapter must be called as a function: adapter() inside the kit.adapter property.

3. Final Answer:

   Correct import and adapter() call in svelte.config.js -> Option B

4. Quick Check:

   Import + adapter() call = correct setup [OK]

Hint: Import adapter and call it as a function in config [OK]

Common Mistakes:

• Forgetting to call adapter() as a function
• Importing wrong adapter package
• Assigning adapter without calling it

3. Given this svelte.config.js snippet, what will be the output folder after building?

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

export default {
  kit: {
    adapter: adapter({
      pages: 'build',
      assets: 'build',
      fallback: null
    })
  }
};

medium

A. The build output will be in the 'build' folder containing static files

B. The build output will be in the 'public' folder with server files

C. The build output will be in the 'dist' folder with dynamic server code

D. No output folder will be created due to missing fallback

Solution

1. Step 1: Analyze adapter options

   The 'pages' and 'assets' options set the output folder to 'build'.

2. Step 2: Understand fallback null

   Fallback null means no SPA fallback page, but static files still output to 'build'.

3. Final Answer:

   The build output will be in the 'build' folder containing static files -> Option A

4. Quick Check:

   pages and assets = 'build' folder output [OK]

Hint: pages and assets options define output folder [OK]

Common Mistakes:

• Confusing fallback with output folder
• Assuming default output folder is 'public'
• Thinking fallback null prevents output

4. You configured the static adapter but your site shows a 404 error on refresh of a nested route. What is the likely cause?

medium

A. You forgot to set a fallback page for SPA routing

B. You did not import the adapter correctly

C. You used the Node adapter instead of static adapter

D. You did not run the build command

Solution

1. Step 1: Understand static hosting limitations

   Static hosting cannot handle nested routes on refresh without a fallback page.

2. Step 2: Identify fallback usage

   Setting a fallback page (like 'index.html') allows SPA routing to work on refresh.

3. Final Answer:

   You forgot to set a fallback page for SPA routing -> Option A

4. Quick Check:

   Missing fallback causes 404 on nested route refresh [OK]

Hint: Set fallback page to fix refresh 404 on nested routes [OK]

Common Mistakes:

• Assuming import errors cause 404 on refresh
• Confusing adapter type with routing issues
• Forgetting to build before testing

5. You want to deploy a SvelteKit blog as a static site with client-side routing fallback. Which svelte.config.js adapter config is correct?

hard

A. adapter: adapter({ pages: 'build', assets: 'build', fallback: null })

B. adapter: adapter({ pages: 'public', assets: 'public', fallback: '404.html' })

C. adapter: adapter({ pages: 'build', assets: 'build', fallback: 'index.html' })

D. adapter: adapter({ pages: 'dist', assets: 'dist' })

Solution

1. Step 1: Identify fallback for SPA routing

   Setting fallback to 'index.html' enables client-side routing fallback for nested routes.

2. Step 2: Confirm output folders

   Using 'build' for pages and assets is common and correct for static output.

3. Final Answer:

   adapter: adapter({ pages: 'build', assets: 'build', fallback: 'index.html' }) -> Option C

4. Quick Check:

   Fallback 'index.html' + build folders = SPA static deploy [OK]

Hint: Use fallback 'index.html' for SPA routing on static deploy [OK]

Common Mistakes:

• Setting fallback to null disables SPA fallback
• Using wrong folder names for output
• Omitting fallback causes refresh 404 errors