2024-01-02
2997
#nextjs
Emmanuel Odioko
169272
111
Jan 2, 2024 ⋅ 10 min read

Using Next.js Route Handlers

Emmanuel Odioko I am a frontend technology enthusiast, intrigued by frameworks and how they work, presently specializing in React, and would love to teach on any topic under it.

Recent posts:

javascript is null or empty function

How to check for null, undefined, or empty values in JavaScript

In most languages, we only have to cater to null. But in JavaScript, we have to cater to both null and undefined. How do we do that?

Lewis Cianci
Feb 14, 2025 ⋅ 4 min read
MERN Stack: Overview With Examples

What is the MERN stack? Overview with examples

Discover how the MERN stack (MongoDB, Express.js, React, Node.js) enables developers to build dynamic, performant, modern websites and apps.

Nefe Emadamerho-Atori
Feb 13, 2025 ⋅ 20 min read
Leveraging Parallel Computing In Node.js

Leveraging parallel computing in Node.js

Use parallel computing in Node.js with worker threads to optimize performance, handle CPU-intensive tasks, and utilize multi-core processors.

David Omotayo
Feb 13, 2025 ⋅ 8 min read

A guide to modern frontend architecture patterns

Frontend architecture is the foundation of your frontend codebase. Here’s how to optimize the pattern that you choose.

Shalitha Suranga
Feb 12, 2025 ⋅ 9 min read
View all posts

3 Replies to "Using Next.js Route Handlers"

  1. I implemented route handler in order to log out the user on the oauth (custom) provider site. It works on localhost (both dev & build), but doesn’t work when deployed on the server. Seems like the function isn’t called, app redirects to the homepage. Any ideas why?

  2. Very helpful article when trying to figure out how to access the values passed as dynamic portions of the reuqest! It’s by adding `{params}` as a second argument to the handler!

    TS throws an error for this. Do Types exist for the { params } argument, Emmanuel?

    Thank you. Martin

Leave a Reply