Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: fix links in zero-installs explanation #6075

Merged
merged 1 commit into from Jan 15, 2024
Merged

Conversation

bitjson
Copy link
Contributor

@bitjson bitjson commented Jan 12, 2024

What's the problem this PR addresses?

I spent a long time debugging a failing yarn install --immutable --immutable-cache --check-cache in my CI environment.

I was seeing the error YN0056: PACKAGE@npm:x.x.x: Cache entry required but missing for PACKAGE@npm:x.x.x for every package in the cache. (The issue was clearly not just for packages with native dependencies like in #4514.)

After trying in multiple environments, I finally realized .pnp.cjs was changing based on the nesting depth of the repo, as enableGlobalCache was not set to false in .yarnrc.yml. (This occurred after an upgrade from Yarn v3 to Yarn v4.)

(Including the above to help anyone searching for this issue on GitHub.)

How did you fix it?

This PR fixes the broken PnP link and makes the offline mirror text a link as well. Hopefully that will help others to realize that to get Zero Installs working they'll need to read that section too.

Checklist

  • I have set the packages that need to be released for my changes to be effective.
  • I will check that all automated PR checks pass before the PR gets reviewed.

@bitjson bitjson changed the title Fix links in zero-installs explanation docs: fix links in zero-installs explanation Jan 12, 2024
@arcanis arcanis merged commit eae38cb into yarnpkg:master Jan 15, 2024
24 checks passed
@SalahAdDin
Copy link

Mine does not use pnp.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants