Have been attemping to work through all of the kinks getting a turborepo setup with nextjs 15 and expo 52. The majority of the issues seem to stem from react 18 vs react 19 and eslint 8 vs eslint 9. We're using pnpm and have a shared lock-file. Currently, with our expo workspace included the nextjs builds fails. Attaching the in the next message due to length restrictions.

It is evident that the issue is dependency related because if we exclude the mobile app workspace and reinstall, the runs succeed. What we are unable to figure out at this point is what the specific dependency is and how to get it working. Previously we had issues where the resolution was to explicitly add eslint as a peer dependency to the nextjs package.json apps in order for all eslint plugin packages to install the correct versions.. Guessing this had to do with package hoisting and pnpm not being able to figure out which version to install, despite it being explicitly called out in the package.json. That said, I believe this issue is related to the react version, however this time, the react and react-dom versions are explicitly pinned in the package.json for the apps/web project, so we're unsure on how to fix this.