dev-prune for VS Code
Autocomplete, validation and hover documentation for .devprune.json — the
per-repository configuration file of dev-prune
(devp), the CLI that reclaims disk space from idle Git repositories by deleting
dependency directories a lockfile can provably rebuild.
The extension maps .devprune.json to a bundled copy of the
dev-prune JSON Schema,
so VS Code's built-in JSON language server provides — offline, with no network
fetch —:
- Autocomplete for every key:
project_name, ignore, disable_hooks,
disable_daemon, override_idle_days, min_size_mb, scan_depth.
- Hover documentation describing what each key does.
- Validation — unknown keys and out-of-range values are underlined, because a
.devprune.json that does not parse makes devp skip the repository rather than
guess at what it meant.
- A status bar item showing what you could reclaim — the reclaimable size
from
devp status --json, with repository and candidate counts in the tooltip.
Clicking it opens a small menu: refresh, dry-run in a terminal, open the
dashboard, install the AI agent skill, open the CLI reference. The same
set lives in the command palette under dev-prune:, alongside a Prune This
Repository command that runs devp run . in a terminal. Reading is all
the extension ever does on its own — anything that deletes runs as a visible
devp command in a terminal you can read before it acts.
- A heads-up when the CLI is missing — a workspace with a
.devprune.json but
no devp on PATH gets a one-time notification, because a config file nothing
acts on looks exactly like a working setup. Everything that invokes the CLI
runs solely in trusted workspaces, "Don't show again" is remembered, and one
setting — devprune.notifications — turns every popup off; the status bar
informs without interrupting.
Files that devp config project writes carry a $schema link already, so those work
without this extension; installing it covers hand-written files too. When a file has
its own $schema key, VS Code prefers that link — the hosted schema it points to is
republished from the same canonical file on every site build, so both paths agree.
Seeing no squiggles on a file you know is wrong? VS Code caches downloaded schemas
for the life of the window. If validation went quiet after a dev-prune release, run
Developer: Reload Window (or JSON: Clear Schema Cache) once — the bundled schema
this extension ships is immune, but a file with its own $schema link fetches remotely.
Install
VS Code: marketplace listing,
or search dev-prune in the Extensions view, or code --install-extension VKrishna04.dev-prune.
VSCodium / Cursor: OpenVSX listing —
the same search and command work there.
Anything without marketplace access: the extension has its own releases, tagged
vscode-v<version>, and each one attaches
dev-prune-vscode-<version>.vsix.
(The releases marked latest are the devp CLI, which is a separate download.)
Take the .vsix and run:
code --install-extension dev-prune-vscode-<version>.vsix
codium --install-extension … and cursor --install-extension … work the same way,
as does Extensions view → ⋯ → Install from VSIX. A side-loaded copy is the same
package the marketplace serves for that version — but it never auto-updates, so
check the releases page now and then for a newer one.
| |
