next-connect | The TypeScript-ready, minimal router and middleware layer for Next.js, Micro, Vercel, or Node.js htt | Runtime Evironment library

You're getting a 404: Page not found error, because the page doesn't exist. Next.JS routing methods, means that api/tours/top-5-cheap will go to /pages/api/top-5-cheap.js. And if it doesn't exist, it returns an error.

NOTE: You can do this without the next-connect package with Next.JS file-based routing system.

Here are two of my possible solutions

• Create a new file and enclose the name in brackets ([]) to make it a dynamic route.

Your models are looking good and as you defined the

So the access_token got renamed to oauth_token & refresh_token got renamed to oauth_token_secret:

i think you generated POST request body in wrong way. Try

You have to call next() with empty arguments instead of next(req, res). Calling next() with a parameter(s) results in onError

Looks like you created a custom backend for your Next.js project probably using Node.js and express. This requires some critical changes throughout the project.

You can read the documentation here. https://nextjs.org/docs/advanced-features/custom-server

I wasn't actually calling the middleware. It was in another file.

I removed cookie-session & kept next-iron-session as I only need 1 session library.

Then I made the export in api/twitter/generate-auth-link routes as a wrapper to handler().get(generateAuthLink) function instead of just generateAuthLink.

And then I changed the frontend to not use fetch but instead use Link.

This fixed it!

I removed index.ts file from pages/api/twitter/ & used default export in both pages/api/twitter/generate-auth-link & pages/api/twitter/get-verifier-token.

This solved it!

I found the issue. Actually I was importing createUser from a wrong file by mistake.

changed