Request parsing in Svelte - Step-by-Step Execution

Concept Flow - Request parsing

User sends HTTP request

↓

SvelteKit server receives request

↓

Parse request URL and method

↓

Extract headers and body

↓

Process data in endpoint or load function

↓

Return response to user

This flow shows how a SvelteKit app receives and parses an HTTP request step-by-step.

Execution Sample

Svelte

export async function POST({ request }) {
  const data = await request.json();
  return new Response(JSON.stringify({ message: data.text }), { status: 200 });
}

This code parses JSON data from a POST request and returns a JSON response.

Execution Table

Step	Action	Input/Condition	Result/Output
1	Receive POST request	Request with JSON body {"text":"hello"}	Request object available
2	Call request.json()	Parse JSON body	Parsed object { text: "hello" }
3	Create response	Use parsed data	Response with JSON {"message":"hello"}
4	Send response	Status 200	Client receives JSON message
5	End	No more steps	Request handling complete

💡 Request fully parsed and response sent, no further processing

Variable Tracker

Variable	Start	After Step 2	After Step 3	Final
request	HTTP request object	Same	Same	Same
data	undefined	{ text: "hello" }	{ text: "hello" }	{ text: "hello" }
response	undefined	undefined	Response object with JSON	Response object with JSON

Key Moments - 2 Insights

Why do we use await request.json() instead of just request.json()?

Because request.json() returns a promise that resolves to the parsed data. Await pauses execution until parsing finishes, as shown in step 2 of the execution_table.

What happens if the request body is not valid JSON?

The await request.json() will throw an error, stopping execution. This is not shown in the table but is important to handle in real apps.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of 'data' after step 2?

A undefined

B Response object

C {"text":"hello"}

D Request object

💡 Hint

Check the 'Result/Output' column at step 2 in execution_table

At which step is the response created?

A Step 3

B Step 2

C Step 1

D Step 4

💡 Hint

Look for 'Create response' action in execution_table

If the request body was empty, what would happen at step 2?

A request.json() returns an empty object

B request.json() throws an error

C Response is sent immediately

D Step 2 is skipped

💡 Hint

Recall key_moments about invalid JSON parsing errors

Concept Snapshot

Request parsing in SvelteKit:
- Use async functions like POST({ request })
- Call await request.json() to parse JSON body
- Extract data from parsed object
- Return Response with JSON string and status
- Handle errors for invalid JSON

Full Transcript

In SvelteKit, when a user sends an HTTP request, the server receives it and parses the URL, method, headers, and body. For JSON data, you use await request.json() inside an async function like POST. This returns the parsed object, which you can use to create a response. The response is sent back to the client with a status code. If the JSON is invalid, an error occurs during parsing. This step-by-step flow helps understand how request parsing works in SvelteKit endpoints.

Practice

1. In SvelteKit, which method is used to parse JSON data from a request object?

easy

A. request.formData()

B. request.text()

C. request.json()

D. request.body()

Solution

1. Step 1: Understand request data types

   JSON data is structured and requires parsing to convert it into usable JavaScript objects.

2. Step 2: Identify the correct parsing method

   request.json() is the built-in method to parse JSON body content from a request.

3. Final Answer:

   request.json() -> Option C

4. Quick Check:

   JSON parsing method = request.json() [OK]

Hint: Use request.json() to parse JSON bodies quickly [OK]

Common Mistakes:

• Using request.text() for JSON causes manual parsing errors
• Confusing formData() with JSON parsing
• Assuming request.body() returns parsed data

2. Which of the following is the correct way to parse form data from a request in SvelteKit?

easy

A. const data = await request.json()

B. const data = await request.formData()

C. const data = request.body()

D. const data = request.text()

Solution

1. Step 1: Identify form data parsing method

   Form data is sent as key-value pairs, often from HTML forms, and requires formData() to parse.

2. Step 2: Confirm correct syntax

   The method await request.formData() returns a FormData object representing the form fields.

3. Final Answer:

   const data = await request.formData() -> Option B

4. Quick Check:

   Form data parsing = request.formData() [OK]

Hint: Use request.formData() to get form fields easily [OK]

Common Mistakes:

• Using request.json() for form data causes errors
• Forgetting to await the formData() promise
• Trying to access request.body() directly

3. Given this SvelteKit handler code:

export async function POST({ request, url }) {
  const jsonData = await request.json();
  const searchParam = url.searchParams.get('id');
  return new Response(`ID: ${searchParam}, Name: ${jsonData.name}`);
}

What will be the response text if the request body is {"name":"Alice"} and the URL is /api?id=42?

medium

A. ID: 42, Name: Alice

B. ID: null, Name: Alice

C. ID: 42, Name: undefined

D. ID: , Name: Alice

Solution

1. Step 1: Parse JSON body

   The code uses await request.json() to get { name: 'Alice' } from the request body.

2. Step 2: Extract query parameter

   url.searchParams.get('id') reads the 'id' parameter from the URL, which is '42'.

3. Step 3: Construct response string

   The response text combines both values: "ID: 42, Name: Alice".

4. Final Answer:

   ID: 42, Name: Alice -> Option A

5. Quick Check:

   Parsed JSON and query param combined = ID: 42, Name: Alice [OK]

Hint: Remember url.searchParams.get('key') reads query strings [OK]

Common Mistakes:

• Assuming searchParams.get returns undefined instead of null
• Not awaiting request.json() causing undefined name
• Confusing query param key spacing (id vs id=)

4. What is wrong with this SvelteKit POST handler code?

export async function POST({ request }) {
  const data = request.formData();
  const username = data.get('username');
  return new Response(username);
}

medium

A. Response should be JSON, not plain text

B. Using formData() instead of json() for JSON body

C. Cannot call get() on formData object

D. Missing await before request.formData()

Solution

1. Step 1: Check formData() usage

   request.formData() returns a promise and must be awaited to get the FormData object.

2. Step 2: Identify missing await

   The code calls request.formData() without await, so data is a promise, not a FormData instance, causing an error on data.get().

3. Final Answer:

   Missing await before request.formData() -> Option D

4. Quick Check:

   Always await async parsing methods like formData() [OK]

Hint: Always await request.formData() to get the data object [OK]

Common Mistakes:

• Forgetting await leads to runtime errors
• Confusing formData() with synchronous methods
• Assuming formData() returns plain object

5. You want to handle a POST request in SvelteKit that can accept either JSON or form data. Which approach correctly parses the request body regardless of content type?

hard

A. export async function POST({ request }) {
if (request.headers.get('content-type')?.includes('application/json')) {
const data = await request.json();
return new Response(JSON.stringify(data));
} else {
const form = await request.formData();
const obj = Object.fromEntries(form.entries());
return new Response(JSON.stringify(obj));
}
}

B. export async function POST({ request }) {
const data = await request.json();
return new Response(JSON.stringify(data));
}

C. export async function POST({ request }) {
const form = await request.formData();
return new Response(JSON.stringify(form));
}

D. export async function POST({ request }) {
const text = await request.text();
return new Response(text);
}

Solution

1. Step 1: Check content-type header

   The code checks if the request content type includes 'application/json' to decide parsing method.

2. Step 2: Parse accordingly

   If JSON, it uses request.json(). Otherwise, it uses request.formData() and converts form entries to an object.

3. Step 3: Return consistent JSON response

   Both branches return JSON stringified data, handling both content types correctly.

4. Final Answer:

   Conditional parsing based on content-type header -> Option A

5. Quick Check:

   Check content-type to parse JSON or form data [OK]

Hint: Check content-type header to choose parsing method [OK]

Common Mistakes:

• Assuming all requests are JSON or form data only
• Not converting formData to object before JSON.stringify
• Ignoring content-type leads to parsing errors