Attempted import error: 'FrigadeChecklist' is not exported from '@frigade/react'

[ronneldavis]

This was working previously on next version 14.0.0, but after updating to next version 14.1.0, it stops working.
I am using @frigade/react version 1.38.31

[tuanvpham]

I ran into the same issue. I downgraded Next version down to 14.0.0 to resolve the issue for now, but hope Frigade team would look into it soon.

[christianmat]

Hey there! We're fixing this in the next release of the SDK this week. We'll post the version here as soon as it's out.

[christianmat]

Meanwhile, this might be a workaround for still using Next.js 14.1: vercel/next.js#61153

[tuanvpham]

@christianmat Thanks for the update. Look forward to the release.

[christianmat]

@tuanvpham @ronneldavis we're still trying to figure out the root cause for the issue with Next.js. Meanwhile, you can consider updating to our beta SDK of 2.0 which will be the next major version of Frigade (although it requires 10-15 minutes of upgrades depending on how many flows you are using): https://frigade-v2-docs.mintlify.app/welcome

This version fully works with Next.js 14.1

[tuanvpham]

It is great to hear you guys are working on the issue. Yea I am looking forward to version 2, hopefully it'll be out of beta soon.

[christianmat]

Sharing this related issue here in case it's helpful for folks: vercel/next.js#60890

[christianmat]

@tuanvpham @ronneldavis confirming that this is a bug introduced by Next.js in 14.1.0 according to the above issue (vercel/next.js#60890).

If you bump to the latest Next.js 14.1.1 canary it will automatically resolve itself. Hopefully Next.js team will soon release a GA version that fixes this.

If you don't want to be on the canary, the linked issue provides a series of workarounds. I tested @frigade/react with the latest canary and it appears to be stable.

[tuanvpham]

Thanks @christianmat. Appreciate it.