Hey, Could you temporarily enable Source code visibility so we can check? Also just to confirm, you have set ENABLE_EXPERIMENTAL_COREPACK in your project Environment, right?

Hey! Yes, I've set that variable:

The setting for Customer Success Code Visibility doesn't exist for me. I've searched all project and team settings. Maybe this doesn't exist for my Hobby plan?

Bump. @swarnava Any news?

I cannot reproduce this unfortunately:

Do you have a minimal repository which I can try? I tried building this branch and it seems setting correct PNPM version.

I've built this reproduction: https://github.com/simonknittel/pnpm-on-vercel-reproduction I've removed everything except for the pnpm stuff.

GitHub

GitHub - simonknittel/pnpm-on-vercel-reproduction: Reproduction for https://community.vercel.com/t/corepack-not-detecting-packagemanager/8870

Reproduction for https://community.vercel.com/t/corepack-not-detecting-packagemanager/8870 - simonknittel/pnpm-on-vercel-reproduction

The reproduction also runs into the same error:

However, I've noticed that there might be an issue with the root directory setting which is causing this error. As you can see in my reproduction and my original repository, the app including pnpm files is in a sub directory called app. I've also set the Root Directory setting to that app directory:

When I remove that setting and move all app files into the root directory of the repository, the build succeeds:

After I've moved the files back and enabled the setting again, the build broke again.

So, it seems to me that, whatever is trying to detect the packageManger property, does not play nicely with the Root Directory setting.

It looks like Vercel can find the package.json but was unable to detect a package manager defined in the file. The packageManager must be defined in your package.json in order to use corepack with Vercel, please see here.

The packageManager is set, you can see here: https://github.com/simonknittel/pnpm-on-vercel-reproduction/blob/main/app/package.json#L105

GitHub

pnpm-on-vercel-reproduction/app/package.json at main · simonknittel/pnpm-on-vercel-reproduction

Reproduction for https://community.vercel.com/t/corepack-not-detecting-packagemanager/8870 - simonknittel/pnpm-on-vercel-reproduction

Yes.

Then, set the packageManager property in the package.json file in the root of your repository.

If it's not monorepo, you can ignore Root Directory and deploy whole app like any traditional repo

But the Root directory is needed since the app incl. it's package.json is located in the subdirectory called app. There is no package.json in the root of the repository.

In that case, have you tried setting packageManager on the root directory's package.json?