I’m running into this same issue. We are using the root directory option. The web/package.json in our repo does have the packageManager property set. However, the build says that it is not set.
Hi @thomas-withpulleyc , Is disabling this settings help?
@swarnava The repo is currently setup in a way that relies on some code outside of the root directory, so the build will fail without that enabled. I also can’t figure out how to disable this just for a preview environment. I can’t really turn it off without affecting deploys going on from the team.
I’m in the process of upgrading yarn to set up workspaces and have some better repo practices but this is the state of the repo today and I can’t really make those changes without this yarn upgrade working. This build is currently happening in a preview env.
Probably also worth noting that there is no package.json at the root-level of the repository, only in the root directory of the app (web)