You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which area(s) are affected? (Select all that apply)
App Router
Additional context
To increase the body limit, do we need to define the api route the old way on the page router (so we can use export config) or is there an alternative in the app router ?
The text was updated successfully, but these errors were encountered:
Can please someone from the Next.js team answer this.
With pages API route it is possible, with server actions we can do it. There is nothing documented for app routers route handlers. Is there anything undocumented or do we need to fallback to pages or server actions?
This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.
Link to the code that reproduces this issue
https://codesandbox.io/s/next-with-api-forked-6cs9k8?file=/pages/api/test.js
To Reproduce
I am reopening the issue #52457 because the final comment : #52457 (comment) was not answered.
Use the link https://codesandbox.io/s/next-with-api-forked-6cs9k8?file=/pages/api/test.js to reproduce
Current vs. Expected behavior
In the pages router we can modify the body size limit with:
However there is no equivalent in the App Router. It does work in development mode but fails during the build
Verify canary release
Provide environment information
Operating System: Platform: linux Arch: x64 Version: #97~20.04.1-Ubuntu SMP Thu Oct 5 08:25:28 UTC 2023 Binaries: Node: 16.16.0 npm: 8.11.0 Yarn: 1.22.19 pnpm: N/A Relevant Packages: next: 13.5.6 eslint-config-next: 13.4.7 react: 18.2.0 react-dom: 18.2.0 typescript: 5.1.6 Next.js Config: output: N/A
Which area(s) are affected? (Select all that apply)
App Router
Additional context
To increase the body limit, do we need to define the api route the old way on the page router (so we can use
export config
) or is there an alternative in the app router ?The text was updated successfully, but these errors were encountered: