Repository navigation
[Bug] Unhandled runtime error when using CldImage component #227
Description
Bug Report
Describe the bug
Whenever I try and use the CldImage component on my Next JS 13 site (using pages) I get an error ```Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object.
Check the render method of he.```
I'm using next-cloudinary 4.13.1 and also cloudinary 1.37.3 to delete images
Is this a regression?
Yes
14.12.0
Steps To Reproduce the error
- Install and setup next-cloudinary
- Add component to file and page throws error
Screenshot or Video Recording
Your environment
- OS: Mac OSX 12.6
- Node version: Node 18
- Npm version: Yarn 1.22.19
- Browser name and version: Brave Browser 1.52.129
Activity
colbyfayock commentedon Jul 8, 2023
hey @smithmanny glad to see it looks like you got this resolved, if this was some kind of issue with the component that i can make clear or easier to use, even if simply something in the docs, would love any feedback!
smithmanny commentedon Jul 8, 2023
I found out that the problem came from updating next from 13.4.4 -> 13.4.9
colbyfayock commentedon Jul 8, 2023
for anyone following along, im able to reproduce this: https://twitter.com/colbyfayock/status/1677783476014030849
im suspecting the issue is in how tsup is bundling or theres a bug in Next.js, not totally sure on this one at the moment
colbyfayock commentedon Jul 8, 2023
looks like this is a known issue: vercel/next.js#52216
fix: Temporary Fix for next/image Error Element Type is Invalid (#229)
chore(release): 4.14.1 [skip ci]
github-actions commentedon Jul 11, 2023
🎉 This issue has been resolved in version 4.14.1 🎉
The release is available on:
Your semantic-release bot 📦🚀
chore(release): 4.14.1 [skip ci]