Next 13 (app folder) + nextcrud

[mfik]

Integration with Next 13 with app folder isn't possible, due to the conventions changing. The handler export is changed to GET, POST, PUT, DELETE, etc.

For next, syntax should probably be something like:

export async function GET (req, res) {
  const nextCrudHandler = await NextCrud({
    adapter: new PrismaAdapter({
      prismaClient: prisma,
    })
  })

  return nextCrudHandler(req, res)
}

[mfik]

Can be fixed with: export { handler as GET, handler as POST } if prisma 5 is supported

[AntonAndreevichMoroz]

Has anyone managed to get APP route to work? I tried exporting as GET, POST, etc. But it turns out that in the code next-crud tries to send the response itself via res.send(), but in NextJS 14 this no longer works, it expects to receive a JSON response from the Response constructor.
Although NextApiResponse types have a send() method, in fact it is not presented and I get an error that res.send() is undefined.

[sovetski]

Any update? It does not work on v14 too, I have 404 error

[morinted]

Workaround is to not use the App folder for the API: use pages/api/[...nextcrud].ts

The rest of my code base is still in the app folder and this works where app/api didn't.

[foyarash]

Hello everybody

Sorry for the delay. I have opened a PR to add compatibility with the App Dir #67

There is a bit of breaking changes for on the callbacks but overall it is working for both App and Page router

[ilomon10]

@foyarash is it ready to use?

[foyarash]

Published on v4.0.0.

Feel free to report any issue.

[malaney]

I too am unable to get v4.0.0 of next-crud to fully work using the App Router. The GET requests work, but POST, PUT and DELETE all fail. From what I can tell, the problem seems to be centered around the getRouteType() method and the matchers it uses to parse the path. Every request appears to evaluate to false and the only API route that will work in spite of the matcher returning false is the GET (READ_ALL) route.

[malaney]

I'm no expert, but here is a small PR that appears to fix the issue.

[foyarash]

Thank you for the report & fix @malaney, this has been deployed in v4.0.1