Closed EvHaus closed 8 months ago
We could not detect a valid reproduction link. Make sure to follow the bug report template carefully.
To be able to investigate, we need access to a reproduction to identify what triggered the issue. We need a link to a public GitHub repository (template for App Router, template for Pages Router), but you can also use these templates: CodeSandbox: App Router or CodeSandbox: Pages Router.
The bug template that you filled out has a section called "Link to the code that reproduces this issue", which is where you should provide the link to the reproduction.
Depending on the reason the issue was closed, you can do the following:
In general, assume that we should not go through a lengthy onboarding process at your company code only to be able to verify an issue.
In most cases, a private repo will not be a sufficient minimal reproduction, as this codebase might contain a lot of unrelated parts that would make our investigation take longer. Please do not make it public. Instead, create a new repository using the templates above, adding the relevant code to reproduce the issue. Common things to look out for:
Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps by opening a new issue.
We look into every Next.js issue and constantly monitor open issues for new comments.
However, sometimes we might miss one or two due to the popularity/high traffic of the repository. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority.
Upvoting issues to show your interest will help us prioritize and address them as quickly as possible. That said, every issue is important to us, and if an issue gets closed by accident, we encourage you to open a new one linking to the old issue and we will look into it.
Link to the code that reproduces this issue
https://stackblitz.com/edit/stackblitz-starters-zt49kv
To Reproduce
I'm using
react-pdf
to generate a PDF file on the server (in a Next.js API route). My PDF has some charts, for which I usereact-pdf-charts
. That library usesrenderToStaticMarkup
fromreact-dom/server
to generate some server-side DOM that it parses and injects into the PDF. This all works great in a regular Node.js or Bun app, but when running inside a Next.js API route, it fails with:I'm the author of
react-pdf-charts
and I can't find any way to get this to work in Next.js. It only seems to be a problem inside Next.js. I'm guessing something to do with RSC thinking that thisrenderToStaticMarkup
call is trying to render on the client... even though it's actually on the server.Note, I'm using:
As without it, the app crashes instead with this error:
Any recommendations on how this can be addressed would be really helpful! Thank you.
Current vs. Expected behavior
Next.js app crashes with the stacktrace above. The expectation is that it doesn't crash and continues to generate the PDF file in my API route.
Provide environment information
Which area(s) are affected? (Select all that apply)
App Router
Which stage(s) are affected? (Select all that apply)
next dev (local)
Additional context
No response