-
| I'm having a strange issue that is stumping me. In an existing working JSX component I brought in a library called  Then when I deployed via my CICD, which creates a new container fresh without a cache, I get an error on the page that uses this component. I tracked it down to the bundle including both React 19 and React 17. It looks like  When I then run a  So it seemed like on initial install of this styled components library, the state of my local packages cache meant nothing new needed to be installed but when I cleared my cache and then ran dev mode again, it had to re-evaluate dependencies and installed React v17.. I've tried pinning versions in my imports but that isn't helping.  Pinning all the React imports to  Any thoughts/ideas are welcome.. Framework's build is a bit opaque to me... Can I provide more information? | 
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
| It looks like the version of  From the  import r,{useState as o,useMemo as i,useEffect as s,useContext as a,createElement as c}from"../[email protected]/_esm.js"The  By all accounts this just seems like an incompatibility, but I'm stumped as to why this worked at first? I just spent the whole day building out several JSX components using this library, and in local dev mode it all worked fine, I was even sharing screenshots with my boss, and now when I publish it, it doesn't work.. and when I clear my local cache it also doesn't work anymore. | 
Beta Was this translation helpful? Give feedback.
-
| I suspect the new (broken) React v19 is the issue here, not styled components... I'll close this for now. I opened an issue for anyone also dealing with React 19 + JSX problems. Mike posted a workaround for now in the issue. | 
Beta Was this translation helpful? Give feedback.
I suspect the new (broken) React v19 is the issue here, not styled components... I'll close this for now.
I opened an issue for anyone also dealing with React 19 + JSX problems. Mike posted a workaround for now in the issue.