fix(config): pnpm workspace

[Fabious]

When trying to contribute, I can't pnpm install on a fresh clone:

 ERROR  packages field missing or empty

[J3m5]

I've cloned the repo and ran pnpm install and I did not reproduce the error you mentioned.
And this error is strange as the current setup doesn't use the monorepo feature, (which the packages field is used for).
The pnpm-workspace.yaml in only there to allow the build script of some dependencies.

What is your version of pnpm?

[J3m5]

My guess is that you are on an older pnpm version.
The error was reported there: pnpm/pnpm#9361 and there pnpm/pnpm#8968
And has been fixed in this PR: pnpm/pnpm#8969

The current package manager version is [email protected]
You can try installing it with the corepack install command

[Fabious]

Yes, I use pnpm@9, so the error comes from that.
Maybe we shouldn't restrict the version and be explicit in the config file with the "packages" field? I think it's better to explicitly reference the packages. Feel free to close this MR if it's not a good idea 😁

[J3m5]

Did you see a message (warning) about your pnpm version when running the pnpm install command?

Another solution could be to enable the packagemanagerstrictversion option, it would prevent the error but it is much stricter.

[Fabious]

Got only the line I pasted as error. Not really helpful ^^'

Restricting pnpm version too strictly could discourage people from contributing.

Maybe specify a range version. Or at the very least document the requirement for contributing in the readme.

[J3m5]

Unfortunately we can't specify a version range.

Or at the very least document the requirement for contributing in the readme

I've create #161 for that but I think we can merge yours

Thanks 😉

[J3m5]

@Fabious Can you fix the lockfile please?

[J3m5]

It is in fact possible to specify a version range: https://github.com/openjs-foundation/package-metadata-interoperability-collab-space/blob/main/devengines-field-proposal.md#typical-example