[WIP] fix: update dependencies to make apps work with turbopack

[agualis]

Dependency updates and minimum fixes to make turbopack work.

Just run pnpm run dev and enjoy the new DX 🚀

TODO

• There is a hydration error.
• Fix deprecation error in style foundations.
• Sentry/nextjs lib is compatible but we should test it carefully and fix warnings.
• Test all routes and scenarios.
• Others?

Note that turbopack is not ready for builds so we need to keep the current webpack config for builds.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
mono-beets-v3	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 20, 2024 0:31am
mono-frontend-v3	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 20, 2024 0:31am
mono-test-v3	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 20, 2024 0:31am

[garethfuller]

They hydration error is an issue in Chakra itself. This PR is blocked unless we can upgrade chakra to fix it.

[garethfuller]

Can't do this because toDataUri returns a promise. That's why Sync was required. Code will have to be refactored if for some reason we've lost toDataUriSync.

[agualis]

They hydration error is an issue in Chakra itself. This PR is blocked unless we can upgrade chakra to fix it.
If that's the only issue I don't see it as a big blocker:
We can create a new script in package.json:
"dev:turbo": "next dev --turbo",
so that developers can chose this optional "experimental" mode (knowing that it has some hydration issues).

The remaining real blocker is:

Can'tdo this because toDataUri returns a promise. That's why Sync was required. Code will have to be refactored if for some reason we've lost toDataUriSync. It comes fromdicebear` update (required to make it compatible with turbopack) and we should be able to fix it to make it work as it used to.

That said, in the medium term I would try to migrate to chakra 3 (only if its compat with nextjs 14/15 is production ready).