-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Next.js App Router react-dom server error #109
Comments
Does it work if you add |
It doesn't. It now displays a different error:
|
I was able to get around the Here's where I got to: https://stackblitz.com/edit/stackblitz-starters-zt49kv?file=package.json It currently fails with:
UPDATE: Unfortunately Next 14.2 still has the same issue. Here's a repo to reproduce the issue: https://github.com/EvHaus/react-pdf-charts-next-14 |
Hi, Have you ever found the solution to this problem? I have a couple charts that I need to render into a PDF in a route handler. This seems like the most elegant option, but I am stuck on the Animate.js issue. |
I am getting this issue "Module not found: Error: Can't resolve 'react/jsx-runtime" and "Module not found: Error: Can't resolve 'react-dom/server" in react app where my react and react-dom both are pointing to version 17. How can I resolve it |
I don't know how to resolve it. It seems to be a bug (or limitation of) Next.js. I've opened an issue with them here. Feel free to upvote it to raise its priority. |
I am not using nextjs I have a react app with version 17 but I am getting the same error |
Can you please create a repo with your setup and share it with me? I can take a look. |
Describe the bug
I'm getting the following error when I try to render a chart using ReactPDFChart in Next.js:
Versions:
I am also using
@joshuajaco/react-pdf-renderer-bundled
instead of regularreact-pdf
because of another bug with Next.js. I'm unsure of whether that has any implications on this particular case.Reproduction
Using some chart, for example:
pdfs/report.tsx
This is how I render it and return it to the client, on a
route.jsx
API "page" (which worked without the charts):some-api/route.jsx
Validations
The text was updated successfully, but these errors were encountered: