Catch-all API routes in NextJS - Performance & Optimization

Performance: Catch-all API routes

MEDIUM IMPACT

Catch-all API routes impact server response time and routing efficiency, which affects how quickly the page can load dynamic data.

Handling multiple dynamic API endpoints with flexible paths

NextJS

export default function handler(req, res) {
  const { slug } = req.query;
  // Use slug array directly to handle dynamic paths flexibly
  res.status(200).json({ path: slug });
}

Simplifies routing logic by handling all paths uniformly, reducing CPU cycles per request.

📈 Performance GainReduces server processing time, improving response speed and lowering LCP.

Handling multiple dynamic API endpoints with flexible paths

NextJS

export default function handler(req, res) {
  const { slug } = req.query;
  if (slug.length === 1) {
    // handle /api/post
  } else if (slug.length === 2) {
    // handle /api/post/comment
  } else {
    res.status(404).end();
  }
}

Manually checking slug length and branching logic causes complex code and slower route matching.

📉 Performance CostAdds extra CPU time per request due to multiple conditional checks, increasing server response latency.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Manual slug length checks with multiple conditions	0 (server-side)	0	0	[X] Bad
Uniform catch-all handler using slug array directly	0 (server-side)	0	0	[OK] Good

Rendering Pipeline

Catch-all API routes affect the server-side routing stage before the browser receives data. Efficient routing reduces server response time, improving the critical rendering path.

→Server Routing

→Data Fetching

→Network Transfer

⚠️ BottleneckServer Routing logic complexity

Core Web Vital Affected

LCP

Catch-all API routes impact server response time and routing efficiency, which affects how quickly the page can load dynamic data.

Optimization Tips

1Avoid complex conditional logic inside catch-all API routes to reduce server CPU time.

2Use the slug array directly to handle dynamic paths uniformly.

3Monitor API response times in DevTools Network tab to catch routing inefficiencies.

Performance Quiz - 3 Questions

What is a main performance drawback of manually checking slug array length in catch-all API routes?

A It causes more DOM reflows in the browser.

B It increases CSS selector complexity.

C It increases server CPU usage due to multiple conditional checks.

D It blocks rendering on the client side.

DevTools: Network

How to check: Open DevTools, go to Network tab, filter API requests, and check the response time of catch-all API routes.

What to look for: Look for lower server response times (Time to First Byte) indicating efficient routing.

Practice

1. What does a catch-all API route file named [...slug].js in Next.js do?

easy

A. It catches all URL paths that match and provides the parts as an array in req.query.slug.

B. It only catches the root API path and ignores nested paths.

C. It catches only one specific URL path exactly matching slug.

D. It disables all API routes in the folder.

Solution

1. Step 1: Understand catch-all route naming

   In Next.js, files named with [...name].js catch all nested paths under that route.

2. Step 2: Check how parameters are passed

   The parts of the URL matched are passed as an array in req.query.name, here slug.

3. Final Answer:

   It catches all URL paths that match and provides the parts as an array in req.query.slug. -> Option A

4. Quick Check:

   Catch-all route = array in req.query [OK]

Hint: Catch-all uses [...name].js and returns array in req.query[name] [OK]

Common Mistakes:

• Thinking it catches only one path instead of many
• Expecting a string instead of an array in req.query
• Confusing catch-all with optional catch-all routes

2. Which of the following is the correct filename for a catch-all API route in Next.js?

easy

A. [slug].js

B. [...slug].js

C. slug.js

D. [slug...].js

Solution

1. Step 1: Recall catch-all route syntax

   Catch-all routes use three dots inside square brackets before the name, like [...slug].js.

2. Step 2: Compare options

   Only [...slug].js matches the correct syntax for catch-all routes.

3. Final Answer:

   [...slug].js -> Option B

4. Quick Check:

   Catch-all filename = [...name].js [OK]

Hint: Catch-all filenames always have three dots inside brackets [OK]

Common Mistakes:

• Using single brackets without dots for catch-all
• Placing dots outside brackets
• Missing brackets entirely

3. Given a catch-all API route file pages/api/[...params].js with this handler:

export default function handler(req, res) {
  res.json(req.query.params);
}

What will be the JSON response for a request to /api/a/b/c?

medium

A. "a/b/c"

B. {"params": "a/b/c"}

C. ["a", "b", "c"]

D. null

Solution

1. Step 1: Understand catch-all parameter passing

   The catch-all [...params] captures all path parts as an array in req.query.params.

2. Step 2: Check the handler response

   The handler returns req.query.params as JSON, so the response is the array of parts.

3. Final Answer:

   ["a", "b", "c"] -> Option C

4. Quick Check:

   Catch-all returns array of path parts [OK]

Hint: Catch-all returns array of URL parts in req.query [OK]

Common Mistakes:

• Expecting a string instead of an array
• Confusing JSON structure returned
• Not recognizing catch-all returns array

4. You wrote a catch-all API route pages/api/[...slug].js but when you request /api (no extra path), you get an error. What is the likely cause?

medium

A. You forgot to export the handler function.

B. The file name is incorrect; it should be [slug].js.

C. API routes cannot have dynamic segments.

D. Catch-all routes require at least one path segment; use optional catch-all [[...slug]].js instead.

Solution

1. Step 1: Understand catch-all vs optional catch-all

   Catch-all [...slug].js requires at least one path part; it does not match the base path alone.

2. Step 2: Identify fix for base path requests

   To handle base path /api with no extra parts, use optional catch-all [[...slug]].js.

3. Final Answer:

   Catch-all routes require at least one path segment; use optional catch-all [[...slug]].js instead. -> Option D

4. Quick Check:

   Catch-all needs path parts; optional catch-all handles empty [OK]

Hint: Use [[...name]].js for optional catch-all including empty path [OK]

Common Mistakes:

• Expecting catch-all to match empty path
• Misnaming the file without brackets
• Ignoring export of handler function

5. You want to create a catch-all API route that returns a JSON object with keys for each path part and their index, for example, for /api/a/b/c it returns {"0": "a", "1": "b", "2": "c"}. Which handler code inside pages/api/[...parts].js achieves this?

hard

A. export default function handler(req, res) {
const obj = {};
req.query.parts.forEach((p, i) => { obj[i] = p; });
res.json(obj);
}

B. export default function handler(req, res) {
res.json(req.query.parts.join(','));
}

C. export default function handler(req, res) {
res.json({ parts: req.query.parts });
}

D. export default function handler(req, res) {
res.json(req.query.parts.length);
}

Solution

1. Step 1: Understand the input and desired output

   The catch-all parameter parts is an array of path parts. We want to create an object with keys as indices and values as parts.

2. Step 2: Check which code builds the object correctly

   export default function handler(req, res) { const obj = {}; req.query.parts.forEach((p, i) => { obj[i] = p; }); res.json(obj); } loops over req.query.parts and assigns each part to the object with its index as key, then returns it as JSON.

3. Final Answer:

   export default function handler(req, res) { const obj = {}; req.query.parts.forEach((p, i) => { obj[i] = p; }); res.json(obj); } -> Option A

4. Quick Check:

   Loop parts to object with index keys = export default function handler(req, res) { const obj = {}; req.query.parts.forEach((p, i) => { obj[i] = p; }); res.json(obj); } [OK]

Hint: Use forEach to map array parts to object keys [OK]

Common Mistakes:

• Returning array or string instead of object
• Not looping to create object keys
• Returning length instead of parts