Static adapter deployment in Svelte - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the static adapter in SvelteKit.

Svelte

import adapter from '@sveltejs/adapter-[1]';

Drag options to blanks, or click blank then click option'

Avercel

Bnode

Cstatic

Dnetlify

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'node' adapter instead of 'static'.

Misspelling the adapter name.

The static adapter is imported from '@sveltejs/adapter-static' to enable static site generation.

2fill in blank

medium

Complete the adapter configuration in svelte.config.js for static deployment.

Svelte

export default {
  kit: {
    adapter: adapter({ [1]: 'build' })
  }
};

Drag options to blanks, or click blank then click option'

Apages

Btarget

Cassets

Dout

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'target' instead of 'pages'.

Omitting the adapter configuration.

The 'pages' option specifies the output folder for the static files, commonly set to 'build'.

3fill in blank

hard

Fix the error in the build script to deploy a static site.

Svelte

"scripts": {
  "build": "svelte-kit [1]"
}

Drag options to blanks, or click blank then click option'

Adev

Bbuild

Cpreview

Dadapter-static

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'preview' or 'dev' instead of 'build'.

Adding adapter name in the script command.

The correct build command is 'svelte-kit build' to generate the static site files.

4fill in blank

hard

Fill both blanks to configure the static adapter with custom folders.

Svelte

adapter: adapter({
  [1]: 'public',
  [2]: 'assets'
})

Drag options to blanks, or click blank then click option'

Apages

Btarget

Cassets

Dfiles

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing 'target' with 'pages'.

Using 'files' instead of 'assets'.

'pages' sets the folder for HTML pages, 'assets' sets the folder for static assets.

5fill in blank

hard

Fill all three blanks to complete the svelte.config.js static adapter setup.

Svelte

import adapter from '@sveltejs/adapter-[1]';

export default {
  kit: {
    adapter: adapter({
      [2]: 'build',
      [3]: 'static'
    })
  }
};

Drag options to blanks, or click blank then click option'

Astatic

Bpages

Cassets

Dnode

Attempts:

3 left

💡 Hint

Common Mistakes

Importing wrong adapter like 'node'.

Mixing up 'pages' and 'assets' keys.

Import the 'static' adapter, then configure 'pages' and 'assets' folders for output.

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