agentleFS
Sign inStart free
LedgerHQLedgerHQ/ledger-live/.agents/skills/pnpm-resolution/SKILL.md

pnpm-resolution

Skill627 starsChanged 9 days agoMITView on GitHub

`.pnpmfile.cjs` hooks and `pnpm.packageExtensions` are deprecated. Read when fixing MODULE_NOT_FOUND, undeclared peers, lockfile churn, or editing `.pnpmfile.cjs`, `pnpm.packageExtensions`, or `.npmrc` hoist patterns.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Do not add a hook, a packageExtensions entry, or a public-hoist-pattern to paper over a missing dependency.

    line 13
  2. Very specific:

    Fix upstream: if a third-party package require()s something it does not list — PR, then bump.

    line 20
  3. Very specific:

    overrides / catalog: only pin versions; they do not replace a missing declaration.

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

pnpm resolution workarounds are deprecated

.pnpmfile.cjs readPackage hooks and pnpm.packageExtensions are deprecated. Burn-down: LIVE-37807.

Do not add a hook, a packageExtensions entry, or a public-hoist-pattern to paper over a missing dependency.

They invent a graph that package.json does not declare. That poisons nx affected (projectsAffectedByDependencyUpdates: "auto") and forces the whole lockfile into the cache hash.

Instead

  1. Declare it on the workspace package that imports it (dependencies, or peerDependencies when a singleton is required).
  2. Fix upstream if a third-party package require()s something it does not list — PR, then bump.
  3. overrides / catalog only pin versions; they do not replace a missing declaration.
  4. Existing entries: shrink them. Moving a .pnpmfile.cjs hook into packageExtensions is the same workaround.

patchedDependencies is a content fork, not this class of workaround. Prefer upstream; do not use a patch to inject undeclared deps. Read dependency-patches before creating or changing one.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free