Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

result.toUnchunkedString is not a function #235

Open
AlexTech314 opened this issue Nov 16, 2024 · 2 comments
Open

result.toUnchunkedString is not a function #235

AlexTech314 opened this issue Nov 16, 2024 · 2 comments

Comments

@AlexTech314
Copy link

I am using nextjs as part of a NestedStack. Please see my exact usage here: https://github.com/AlexTech314/ProjectBase

Upon completing deployment, the NextjsServer Lambda is throwing the following error in Cloudwatch logs:

2024-11-16T02:36:08.461Z 300f0821-105f-4b1d-a88f-62ba3cac482a ERROR ⨯ TypeError: result.toUnchunkedString is not a function at sendRenderResult (/var/task/node_modules/next/dist/server/send-payload.js:66:54) at NextNodeServer.sendRenderResult (/var/task/node_modules/next/dist/server/next-server.js:581:50) at NextNodeServer.pipeImpl (/var/task/node_modules/next/dist/server/base-server.js:975:24) at async NextNodeServer.handleCatchallRenderRequest (/var/task/node_modules/next/dist/server/next-server.js:281:17) at async NextNodeServer.runImpl (/var/task/node_modules/next/dist/server/base-server.js:945:9) at async NextNodeServer.handleRequestImpl (/var/task/node_modules/next/dist/server/base-server.js:879:20) at async fVe (index.mjs:66:10292) at async Runtime.F7 [as handler] (index.mjs:66:10147)

I've found a recently opened and resolved issue in opennext-aws pertaining to a similar problem. opennextjs/opennextjs-aws#507

I attempted to follow the app-router example laid out to no avail.

Is this a know issue?

@AlexTech314
Copy link
Author

It seems that an upgrade to open-next 3.1.3 would solve the issue, but I am not totally sure.

@up1io
Copy link

up1io commented Nov 21, 2024

I faced a similar problem and rolled back to the following version for the frontend and now it seems to work.

"next": "14.2.18",
"open-next": "^2.3.9",

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants