Yarn .gitignore template

The .yarn/* rule with five negations is the same construction the VS Code template uses, and for the same reason. Ignoring the directory outright would stop git descending into it, so no negation below could work. Ignoring the contents keeps the directory visible and lets the exceptions apply.

The five kept directories are the ones that are genuinely part of the project. patches holds patch files applied to dependencies after install, which are source and would be lost forever if untracked. plugins holds tool extensions the project depends on. releases holds a pinned copy of the package manager itself, so everyone runs the same version. sdks holds editor integration shims, and versions holds the release workflow's version bump files.

What is not listed is the cache, and that is where the judgement call sits. The zero install workflow deliberately commits .yarn/cache, so a clone can install with no network access at all and CI needs no install step. Teams that use it accept a larger repository in exchange for reproducibility and speed. Teams that do not want the size ignore the cache and install normally.

.pnp.* covers the Plug'n'Play resolution files, which replace the node_modules directory entirely by mapping every import to a location inside the cache. Whether they should be ignored follows the same decision: in a zero install setup they are committed alongside the cache, because they are what makes the cache usable.

node_modules is kept in the list because a project can switch resolution modes, and the debug and error log rules cover the files written when an install fails. The lockfile itself, yarn.lock, is deliberately absent from every rule here, which is correct: it must be committed.