fleet-tidying-rolldown-bundles

Report dedupable lockfile transitives in fleet bundle repos.

125|42|Updated May 19, 2025
One-click install
npx skills add https://github.com/SocketDev/socket-mcp --skill fleet-tidying-rolldown-bundles
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fleet-tidying-rolldown-bundles
Source: https://github.com/SocketDev/socket-mcp/tree/main/.agents/skills/fleet-tidying-rolldown-bundles
Command: npx skills add https://github.com/SocketDev/socket-mcp --skill fleet-tidying-rolldown-bundles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps fleet rolldown bundles lean by reporting lockfile transitives that can be deduped, validating that external/ re-export shims remain delegated to shared packs, and ensuring that only lockfile mutations occur via pnpm dedupe while reporting any changes that would affect published bundles. Conservative and no-prompt: the only mutation is a lockfile-only pnpm dedupe; anything that would change the published bundle is reported for a human. Use for periodic dependency hygiene on bundle repos, or before a release.

Core Features & Use Cases

  • Detects and reports dedupable lockfile transitives to reduce bundle size and avoid version drift.
  • Validates that Socket-published prefixes are routed through catalog overrides and flags overrides that may drift.
  • Flags fat re-export shims in external/ that regress to self-contained bundles, ensuring lean shared packs.
  • Dry-run by default; with --fix, executes pnpm dedupe (lockfile-only) and recommends a follow-up bundle rebuild.

Quick Start

Run the dry-run to identify dedupe opportunities across fleet repos, and use --fix to apply a lockfile-only dedupe.

Frequently Asked Questions about fleet-tidying-rolldown-bundles

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I dedupe lockfile transitives in pnpm bundle repos?▼

To dedupe lockfile transitives in pnpm bundle repos, run a dry-run to identify dedupable dependencies, then use a lockfile-only --fix operation to safely apply pnpm dedupe without altering published bundles.

What causes version drift and fat bundles in fleet rolldown repos?▼

Version drift and fat bundles in fleet rolldown repos are caused by un-deduped lockfile transitives and external/ re-export shims regressing into self-contained bundles instead of delegating to shared packs.

Can I automatically fix external/ re-export shims during pnpm dedupe?▼

You cannot automatically fix external/ re-export shims during pnpm dedupe because the tool only mutates lockfiles. Fat shim regressions are reported for human review to protect published bundle integrity.

How do I validate catalog overrides for Socket-published prefixes?▼

Validate Socket-published prefixes by checking that they route through catalog overrides. The tool flags overrides that may drift away from the catalog to ensure dependencies remain lean and consistent.

Do I need a specific fleet roster file to run dependency hygiene checks?▼

You need the canonical fleet roster located at cascading-fleet/lib/fleet-repos.txt and pnpm installed. These prerequisites allow the tool to identify dedupe opportunities across multiple repos safely.

What is the safest way to run pnpm dedupe before a release?▼

The safest way to run pnpm dedupe before a release is using a dry-run by default to report findings. Apply changes with --fix to execute a lockfile-only mutation and recommend a follow-up bundle rebuild.