Closed AugusDogus closed 1 year ago
This issue has been labeled as a bug since it was created using the 🚨 Bug Report Template.
Hi there, thank you so much for the report!
Following our Maintenance Process, we will review your bug report and get back to you next Wednesday. To ensure a smooth review of your issue and avoid unnecessary delays, please make sure your issue includes the following:
package.json
file.If you have identified the cause of the bug described in your report and know how to fix it, you're more than welcome to open a pull request address it. Check out our quick start guide for a simple contribution process.
If you think your issue is a question (not a bug) and would like quicker support, please close this issue and forward it to an appropriate section on our community forum: https://community.prismic.io
- The Prismic Open-Source Team
Same issue here. I also tried removing some cached folders such as .next/
and node_modules/
without any luck. Downgrading to 13.4.8 only worked.
Fixed as of v1.3.3
in https://github.com/prismicio/prismic-next/pull/79.
Versions
@prismicio/next
: 1.3.2next
: 13.4.8Reproduction
Attempt to use PrismicNextImage with Next 13.4.8
What is actually happening?
next dev
&next build
both fail with the error:Warning: React.jsx: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: object. at PrismicNextImage (/Users/augie/dev/redacted/node_modules/.pnpm/@prismicio+next@1.3.2_@prismicio+client@7.1.0_next@13.4.8_react@18.2.0/node_modules/@prismicio/next/dist/PrismicNextImage.cjs:23:29)