Initial Interactions endpoint URL check sends invalid body about discord-api-docs HOT 6 CLOSED

Discord does not send a body of [object EventEmitter]. Can you come up with less complex repro steps so we can eliminate all of these frameworks?

from discord-api-docs.

Ive tested this out without hono just using raw nextjs api functions and still got the same result, going to test it out with the default bun server next

from discord-api-docs.

Bun.serve({
    fetch(req) {
        console.log('content-type', req.headers.get('content-type'))
        console.log('body', req.body)
        console.log('method', req.method)
        return Response.json({
            test: 1
        })
    },
    port: 3000
})

Still gives the same response:

For some reason discord is giving back a ReadableStream thats literally just [object EventEmitter] when turned into text. Instead of actual json like its supposed to.
Theres a possibility this could be a ngrok problem but I doubt it.

from discord-api-docs.

Can you please provide the actual text of the body? A ReadableStream is expected.

from discord-api-docs.

This is the expected behavior, since Bun uses the Web specification of Request. So Request#body is of type ReadableStream.

If you want the JSON body of the request, you must use Request#json.

Bun.serve({
    async fetch(req) {
        console.log('content-type', req.headers.get('content-type'))
-       console.log('body', req.body)
+       console.log('body', await req.json())
        console.log('method', req.method)
        return Response.json({
            test: 1
        })
    },
    port: 3000
})

from discord-api-docs.

This fixes it, so i'm assuming this isn't a problem with discord, probably hono/nextjs. Thanks. (ill post edit this post with a solution if anyone else encounters this)

EDIT: for some reason running nextjs with bun via bun --bun dev totally breaks nextjs api routes. Removing the --bun seems to fix it. Probably need to post an issue on nextjs at some point

from discord-api-docs.