Migrate from yarn to pnpm

[nolanlawson]

We are still using yarn v1 in this repo – we should migrate to a more modern solution.

After internal discussion we decided on pnpm. Two challenges:

1. Volta has experimental pnpm support – developers will have to enable an env variable.
2. The tachometer build script will need to be agnostic to pnpm vs yarn since it might test against older commits that are still using yarn. We can use the presence or absence of yarn.lock to test for this
3. GitHub Actions needs to use whatever version of pnpm we are using in our Volta config

[harshsbhat]

Would like to work on this. Is this issue ready to work on?

[nolanlawson]

@harshsbhat Sure, this is available. Thanks in advance!

[SourabhMulay]

Hi @nolanlawson ,

I hope you're doing well!

I’ve attempted to migrate to pnpm, but after running pnpm install for some dependencies, I encountered the following error:

ERR_PNPM_FETCH_404  GET https://registry.yarnpkg.com/@lwc%2Flwc-modules-bar: Not Found - 404"
@lwc/lwc-modules-bar  is not in the npm registry, or you have no permission to fetch it.
No authorization header was set for the request.

It seems that @lwc/lwc-modules-bar is not available in the npm registry, or I may not have the necessary permissions to fetch it. Additionally, no authorization header was set for the request.
Could you please provide any insights or suggestions on how to resolve this issue?

Thank you for your help!

[wjhsf]

That's not a real module, it's just used in a test fixture. You'll need to configure pnpm to ignore package.json files found in any __tests__ directory.

lwc/packages/@lwc/module-resolver/src/__tests__/fixtures/mapping/package.json

Lines 7 to 8 in 3ca1070

	"@lwc/lwc-modules-foo": "1.0.0",
	"@lwc/lwc-modules-bar": "1.0.0"

Also, seems weird to be using pnpm, but using the yarn registry. 🤷