Multirepo pnpm install fails after creation about field-plugin HOT 8 CLOSED

Hey @eunjae-lee

I'll post the package.json later today. I tested it on two MacOs devices (one with nvm and corepack and one with "normal" node and pnpm installations). I'll try it with my Win PC later today and update my report.

from field-plugin.

Hello @hoersamu Thanks for reporting this issue.
I just tested it and it actually worked on my machine.

• standalone + vue 3 template
• monorepo + vue 3 template

both worked. I'm using Node 18.16.0 with pnpm 8.6.7, which isn't that different from yours.

Maybe could you post your package.json that possibly could've caused this issue of Invalid package manager specification in ../../package.json; expected a semver version error"?

from field-plugin.

Hey @eunjae-lee

Sorry for the delay. This is the root package.json file:
package.json

I can't reproduce the polyrepo problem but the monorepo problem is still reproducible.

I asked my collegues to test this too:
Node 18.15.0 + pnpm 8.12.0 -> No Problem
Node 18.15.0 + pnpm 8.14.0 -> Error
Node 18.15.0 + pnpm 8.6.11 -> Error
Node 18.15.0 + pnpm 8.6.5 -> Error

There is also a schema warning in the package.json:

String does not match the pattern of "(npm|pnpm|yarn|bun)@\d+\.\d+\.\d+(-.+)?".

I looked up the spec (https://nodejs.org/api/packages.html#packagemanager) and the officially need name@version.

from field-plugin.

Hm this issue might be related to corepack.
Most of my organization has corepack enabled so this might explain why we can all reproduce it with various pnpm versions.

from field-plugin.

@hoersamu Oh, I don't have corepack enabled. It might be the reason why I cannot reproduce it.

Do you think if we update the package.json to include [email protected] instead of pnpm, will it solve your problem?

from field-plugin.

@eunjae-lee Honestly i would remove it. This field in the package.json is marked as experimental and corepack specific.

If you want to keep it you could also set it to * (or latest or stable).

from field-plugin.

@eunjae-lee Honestly i would remove it. This field in the package.json is marked as experimental and corepack specific.

If you want to keep it you could also set it to * (or latest or stable).

Thanks for the feedback. Then could you give it a test by removing that field, and see if it works for you?

from field-plugin.

Hey @eunjae-lee
* Apparently star also doesn't work but I created a PR where I set the pnpm version to the latest stable release. This fixes the issue.

from field-plugin.