Does not work with Next 15

[xzenon]

Seems like it is not possible to use next-rest-framework with the latest Next because of Async Request APIs breaking changes in version 15.

Any attempt to call API with parameters gives the following error:

{
  "message": "Invalid path parameters.",
  "errors": [
    {
      "code": "invalid_type",
      "expected": "object",
      "received": "promise",
      "path": [],
      "message": "Expected object, received promise"
    }
  ]
}

Could somebody please advice how to resolve this issue?

[oalexdoda]

Similar issue here, it breaks the build command.

Any clue @blomqma ?

[mushan0x0]

I've encountered the same issue. This library is fantastic, and I can't do without it, so I'm temporarily using the next14 version. Are there any plans to fix it soon @blomqma ?

[callumgare]

We're running into the build issue @oalexdoda mentions so I've put together a little workaround. Unfortunately I don't have the capacity to properly get my head around the the codebase well enough to put together tests and things for a PR but until there's official support for Next.js 15 I've forked and patched the library to get around this: https://github.com/infoxchange/next-rest-framework-patch/

You can use it by swapping your existing package.json dependency ("next-rest-framework": "^6.0.5",) with "next-rest-framework": "npm:@infoxchange/next-rest-framework-patch@^6.0.6",

No promises on whether it works in your situation or not but posting it here encase it's useful to others.

[suplere]

Any news about this issue? Swaping library don't solve problem at my side with Next15 and async params or searchParams.

[markedwards]

This is also a major blocker for us. Will this be addressed?

[callumgare]

Thank you @mushan0x0 and @blomqma!