You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have upgraded an older next.js site to the latest v15.1.6 version. I had many struggles with i18n and next-intl, but i think i maybe found a bug with clover-iiif.
Investigated further. Changing the import solved it, x.default.
constViewer=dynamic(// () => import("@samvera/clover-iiif").then((Clover) => Clover.Viewer), // works in Next v14, not in v15()=>import("@samvera/clover-iiif/viewer").then((Clover)=>Clover.default),{ssr: false,});
I guess something can be done to make it behave the same in v14 and v15, else an update to the docs could mention this difference?
Update: i see this already was discovered by @brogr: #234. Should have paid more attention to the other issues, sry.
I have upgraded an older next.js site to the latest v15.1.6 version. I had many struggles with i18n and
next-intl
, but i think i maybe found a bug withclover-iiif
.I have no idea why, but i can document my recreation (https://github.com/tarjelavik/clover-iiif-debug):
npx create-next-app@latest clover-iiif-debug --use-npm cd clover-iiif-debug npm i next-intl @samvera/clover-iiif
I installed
next-intl
as i though that it messed up, but that seemed to not have any influence on the issue.FIx
In the end downgrading
next
andreact
to v14 and v18 is a possible fix.The text was updated successfully, but these errors were encountered: