Next JS Api Routes - POST - Invalid Body response with request body payload

[matthewgisonno]

Next JS Api Routes - POST - Invalid Body response with request body payload

[matthewgisonno]

Ok, following up here... I'm not sure this is actually a bug, but more of a "feature" of how fastify handles / parses data. After reviewing this document: https://www.fastify.io/docs/latest/Reference/ContentTypeParser/

I was able to fix the issue I was facing by killing all the content parsers and adding a generic parser. Like so:

  await app.register(fastifyNext, {}).after(async () => {
    app.removeAllContentTypeParsers();

    app.addContentTypeParser('*', function (request, payload, done) {
      done();
    });

    await app.next('/api/user', { method: 'POST' });
  });

Does this sound right or should this @fastify/nextjs plugin handle the POST method separately from the fastify server itself? Any feedback or comments wishing to explain further would be greatly appreciated.

[Eomm]

No, I don't think that is the right approach - at least it should not work with a paylod

I checked a bit without success, but I would investigate the interface instead

fastify.next('/hello', (app, req, reply) => {
  // your code
  // `app` is the Next instance
  app.render(req.raw, reply.raw, '/hello', req.query, {})
})

[matthewgisonno]

I saw that example, but I was unsure how to access req.raw and if that is just overwriting the request that is being forwarded to the next server, it's still eating the payload, so req.body should be the payload I send in my POST to the API route, but it creates a 400 error - Invalid Body.

Also worth mentioning, NextJS out of the box handles a POST request to an API Route with a payload. So in a normal NextJS app, you can access req.body without issues.

[christmoore]

Encountered the same in NextJS 13. vercel/next.js#24894 (comment) helped resolve this issue for me.