Node adapter deployment in Svelte - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the Node adapter in SvelteKit.

Svelte

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

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

Anetlify

Bstatic

Cvercel

Dnode

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'static' adapter which is for static site generation.

Using 'vercel' or 'netlify' adapters which are for specific platforms.

The Node adapter is imported from '@sveltejs/kit/adapter-node' to enable deployment on Node.js servers.

2fill in blank

medium

Complete the code to configure the Node adapter in svelte.config.js.

Svelte

import adapter from '@sveltejs/kit/adapter-node';

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

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

AoutDir: 'output'

Bout: 'build'

CoutDir: 'build'

Dout: 'output'

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'outDir' instead of 'out' as the option key.

Setting the output directory to a non-standard folder.

The Node adapter uses 'out' to specify the output directory, commonly set to 'build'.

3fill in blank

hard

Fix the error in the start script to run the built Node server.

Svelte

"scripts": {
  "start": "node [1]"
}

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

Abuild/index.js

Bindex.js

Cserver.js

Dbuild/server.js

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'build/server.js' which does not exist in the build folder.

Running files without the 'build/' prefix.

The Node adapter outputs the server file as 'build/index.js', so the start script should run that file.

4fill in blank

hard

Fill both blanks to complete the deployment command and environment variable for production.

Svelte

NODE_ENV=[1] npm run [2]

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

Aproduction

Bstart

Cdevelopment

Dbuild

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'development' instead of 'production' for NODE_ENV.

Running 'build' script instead of 'start' to launch the server.

Set NODE_ENV to 'production' and run the 'start' script to launch the server in production mode.

5fill in blank

hard

Fill all three blanks to complete the minimal svelte.config.js for Node adapter deployment.

Svelte

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

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

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

Anode

Bout

Cbuild

Dstatic

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'static' adapter instead of 'node'.

Using wrong option key like 'outDir' instead of 'out'.

Setting output folder to 'static' instead of 'build'.

The Node adapter is imported as 'node', configured with 'out' set to 'build' folder.

Practice

1. What is the main purpose of using the @sveltejs/adapter-node in a Svelte project?

easy

A. To convert Svelte components into React components

B. To deploy the Svelte app on a Node.js server

C. To enable Svelte apps to run in the browser only

D. To add CSS styling automatically to the app

Solution

1. Step 1: Understand adapter purpose

   The @sveltejs/adapter-node is designed to prepare Svelte apps to run on Node.js servers.

2. Step 2: Compare options

   Options describing conversion to React, browser-only support, or automatic CSS styling are unrelated. Only deploying the Svelte app on a Node.js server correctly states the adapter's purpose.

3. Final Answer:

   To deploy the Svelte app on a Node.js server -> Option B

4. Quick Check:

   Node adapter = deploy on Node.js server [OK]

Hint: Node adapter = run Svelte app on Node.js server [OK]

Common Mistakes:

• Thinking adapter converts Svelte to React
• Assuming adapter only works in browsers
• Confusing adapter with styling tools

2. Which of the following is the correct way to configure the Node adapter in svelte.config.js?

easy

A. import adapter from '@sveltejs/adapter-node'; export default { kit: { adapter: adapter() } };

B. import adapter from '@sveltejs/adapter-node'; export default { kit: { adapter: adapter } };

C. import adapter from '@sveltejs/adapter-node'; export default { kit: { adapter() } };

D. import adapter from '@sveltejs/adapter-node'; export default { adapter: adapter() };

Solution

1. Step 1: Check correct adapter usage

   The Node adapter must be imported and called as a function inside the kit.adapter property.

2. Step 2: Validate syntax

   import adapter from '@sveltejs/adapter-node'; export default { kit: { adapter: adapter() } }; correctly uses adapter: adapter(). Incorrect configurations have invalid object syntax like { adapter() }, fail to call adapter as a function, or place it outside kit.

3. Final Answer:

   import adapter from '@sveltejs/adapter-node'; export default { kit: { adapter: adapter() } }; -> Option A

4. Quick Check:

   Call adapter() inside kit.adapter [OK]

Hint: Always call adapter() inside kit.adapter in svelte.config.js [OK]

Common Mistakes:

• Forgetting to call adapter as a function
• Placing adapter outside the kit object
• Using adapter without parentheses

3. Given the following commands run in a Svelte project configured with the Node adapter:

npm run build
node build/index.js

What will happen when you run node build/index.js?

medium

A. The build folder is deleted

B. An error occurs because index.js does not exist

C. The app runs in the browser automatically

D. The Svelte app starts a Node.js server serving the built app

Solution

1. Step 1: Understand build output

   Using the Node adapter, npm run build creates a Node.js server app in the build folder, including index.js.

2. Step 2: Running the server

   Running node build/index.js starts the Node.js server that serves the Svelte app.

3. Final Answer:

   The Svelte app starts a Node.js server serving the built app -> Option D

4. Quick Check:

   Build + node index.js = start server [OK]

Hint: Build creates server; node index.js starts it [OK]

Common Mistakes:

• Thinking index.js is missing after build
• Expecting app to open in browser automatically
• Confusing build folder with source code

4. You configured @sveltejs/adapter-node in svelte.config.js but running node build/index.js gives an error: Cannot find module 'devalue'. What is the likely cause?

medium

A. You forgot to install dependencies with npm install

B. You did not import the adapter correctly in svelte.config.js

C. You ran npm run dev instead of npm run build

D. The Node.js version is too old

Solution

1. Step 1: Understand the error

   The error means Node.js cannot find the devalue package, which the adapter-node server depends on.

2. Step 2: Check dependencies

   This usually happens if npm install was not run to install all required packages.

3. Final Answer:

   You forgot to install dependencies with npm install -> Option A

4. Quick Check:

   Missing module error = run npm install [OK]

Hint: Missing module? Run npm install before starting server [OK]

Common Mistakes:

• Assuming adapter import error causes missing module
• Confusing dev and build commands
• Ignoring dependency installation step

5. You want to deploy your Svelte app with the Node adapter but need to customize the server port to 4000. Which code snippet correctly sets the port when starting the server?

hard

A. In build/index.js, add const port = 4000; and pass it to the server start function

B. Modify the package.json scripts to include --port 4000

C. Set process.env.PORT = 4000 before running node build/index.js

D. Change the port in svelte.config.js inside the adapter options

Solution

1. Step 1: Understand Node adapter port config

   The Node adapter server reads the port from the environment variable PORT by default.

2. Step 2: Set environment variable before start

   Setting process.env.PORT = 4000 or running PORT=4000 node build/index.js sets the port correctly.

3. Final Answer:

   Set process.env.PORT = 4000 before running node build/index.js -> Option C

4. Quick Check:

   Port set via environment variable PORT [OK]

Hint: Set PORT env variable before starting server [OK]

Common Mistakes:

• Trying to set port in svelte.config.js (not supported)
• Modifying build/index.js directly (not recommended)
• Adding port flags in package.json scripts without env