-
-
Notifications
You must be signed in to change notification settings - Fork 266
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(repo): upgrade to latest Node 22 LTS #15749
Conversation
🚀 Expo preview is ready!
|
c76e372
to
a5d9a70
Compare
Can someone from Connect team fix that one failing build? @trezor/suite-connect |
yes. soon (days, not hours) |
I am not sure how this problem is related with update to the next node version and we are not seeing it in current builds. It looks like next.js is not able to prepare static builds because there are imports from react-lottie (via @trezor/components) that depend on
Not sure, do we need to import everything from @trezor/components dynamically?
? cc @martykan |
I don't think dynamic imports would be a nice solution for this. Seems like they are working on some fix in Lottie, but it's not released yet Gamote/lottie-react#101 |
bf9f0f1
to
9e1ce6c
Compare
Description
Related Issue
Resolve
Screenshots: