Request parsing in Svelte - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is request parsing in SvelteKit?

Request parsing means reading and understanding the data sent by the user to your app, like form inputs or URL info, so your app can respond correctly.

beginner

How do you access URL query parameters in a SvelteKit load function?

You use url.searchParams inside the load function to get query parameters from the URL.

intermediate

Which SvelteKit function helps you read POST request data on the server?

The actions export lets you handle POST requests and parse form data or JSON sent by the user.

intermediate

What method do you use to parse JSON data from a request in SvelteKit?

You call await request.json() inside an action or endpoint to get JSON data from the request body.

beginner

Why is it important to parse requests carefully in SvelteKit?

Parsing requests carefully helps your app understand user input correctly, avoid errors, and keep data safe.

In SvelteKit, where do you typically parse URL query parameters?

A In the component's script tag directly

B Inside the load function using url.searchParams

C Inside the onMount lifecycle hook

D Using window.location.href

URL query parameters are accessed in the load function via url.searchParams for server-side parsing.

Which method reads JSON data from a POST request in SvelteKit?

A request.text()

B request.formData()

C request.json()

D request.body()

Use request.json() to parse JSON data from the request body.

What is the purpose of the 'actions' export in a SvelteKit page?

A To define server-side request handlers like POST

B To handle client-side events

C To style the page

D To fetch data from APIs

The 'actions' export defines server-side handlers for form submissions or POST requests.

How do you parse form data sent via POST in SvelteKit?

A await request.formData()

B await request.json()

C request.body()

D request.params

Use await request.formData() to get form data from a POST request.

Why should you validate parsed request data in SvelteKit?

A To improve app performance

B To reduce server load

C To make the UI look better

D To prevent errors and security issues

Validating parsed data helps avoid errors and protects your app from malicious input.

Explain how to parse and use URL query parameters in a SvelteKit load function.

Think about how the load function receives the URL and how you can read parameters from it.

Describe how to handle and parse POST request data in SvelteKit actions.

Focus on the server-side function that handles form submissions or API calls.

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