Unified types for getServerSideProps and api endpoints

[benjamintd]

Hi!

I am using the following pattern for some pages:

• use getServerSideProps to get (authenticated) resources from my server.
• use SWR on that page on the same resources to keep the data updated and do optimistic updates when the user saves or updates the data.

SWR calls an api endpoint which takes (req: NextApiRequest, res: NextApiResponse) as arguments.

Meanwhile, getServerSideProps uses a context which contains "vanilla" req, res arguments (with types HTTPIncomingMessage and HTTPResponse).

This prevents code reuse between my API handler and getServerSideProps, especially concerning authentication since I am using the nextjs-auth0 library which expects NextAPIRequest and NextApiResponse arguments.

My questions are the following:

• Is this pattern a good practice? Or should I do that differently?
• Is there a structural reason for the req, res arguments to have different types, or could the getServerSideProps context be augmented to have a similar req, res signature?

Thanks!