Apply API middlewares to getServerSideProps

Feature request

API request handlers use middleware (such as cookie parsing). I was surprised to find that getServerSideProps does not apply similar middleware as well, and I believe this would be a rather straightforward and desirable feature to include by default.

For instance, if I were to create a new API endpoint, the cookie parser attached to the req object is available to use.

// pages/api/endpoint.js
export default (req, res) => {
  if (req.cookies.myCookie) {
    // do something with cookie
  }
  res.statusCode = 200
  res.setHeader('Content-Type', 'application/json')
  res.end(JSON.stringify({ name: 'John Doe' }))
} 

However, it seems the cookie parser (API middleware) is not applied to getServerSideProps and so the following example does not work as desired:

// pages/Page.js
export async function getServerSideProps({ req, res }) {
  if (req.cookies.myCookie) { /* cookie parser object not available */ }

  res.statusCode = 200
  res.setHeader('Content-Type', 'application/json')
  res.end(JSON.stringify({ name: 'John Doe' }))

Describe the solution you’d like

Apply API middleware to getServerSideProps by default.

Thanks!

Thank you for all of your amazing work on next.js!

[em]

It looks like req.query is still missing. Only cookies was added. Can you reopen this issue? The ability to write common utilities that operate both in page and api routes is stifled by them not having the same properties & types due to this middleware mismatch.

[karlhorky]

Wow @BoiForus thanks for the tip - looks like https://github.com/vercel/next.js/pull/19724 (by @mattfwood, reviewed + merged by @timneutkens ) also added the types req.cookies to getServerSideProps 🎉 🙌 Should be available in next@10.0.4 🚀

@aperaham is this enough? Can this issue be closed now?