dev-prune-linux-x64 1.9.0 → 1.10.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +213 -29
- package/bin/dev-prune +0 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -66,7 +66,7 @@ a single Rust binary, installs its own background schedule, and answers to two n
|
|
|
66
66
|
|
|
67
67
|
<div align="center">
|
|
68
68
|
|
|
69
|
-
**Start here** [Install](#install) · [Editors](#in-your-editor) · [60-second tour](#60-second-tour) · [What it looks like](#what-it-looks-like)
|
|
69
|
+
**Start here** [Install](#install) · [Where it is published](#every-place-it-is-published) · [Editors](#in-your-editor) · [60-second tour](#60-second-tour) · [What it looks like](#what-it-looks-like)
|
|
70
70
|
|
|
71
71
|
**How it thinks** [Why it is safe](#why-it-is-safe) · [Features](#features) · [Commands](#commands) · [Ecosystems](#supported-ecosystems) · [Monorepos](#repositories-with-more-than-one-ecosystem)
|
|
72
72
|
|
|
@@ -120,6 +120,9 @@ problem.
|
|
|
120
120
|
|
|
121
121
|
```bash
|
|
122
122
|
npm install -g dev-prune # or: npx dev-prune status
|
|
123
|
+
bun add -g dev-prune # same package, through bun
|
|
124
|
+
pnpm add -g dev-prune
|
|
125
|
+
yarn global add dev-prune # Yarn 1.x
|
|
123
126
|
uv tool install dev-prune # or: uvx dev-prune status
|
|
124
127
|
pipx install dev-prune
|
|
125
128
|
pip install dev-prune
|
|
@@ -127,9 +130,10 @@ cargo binstall dev-prune # fetches the prebuilt release archive
|
|
|
127
130
|
cargo install dev-prune # builds from source, needs Rust 1.88+
|
|
128
131
|
```
|
|
129
132
|
|
|
130
|
-
The npm and
|
|
131
|
-
|
|
132
|
-
|
|
133
|
+
The [npm](https://www.npmjs.com/package/dev-prune) and
|
|
134
|
+
[PyPI](https://pypi.org/project/dev-prune/) packages **contain the binary** — there is no
|
|
135
|
+
download step at install time, so they work under `npm ci --ignore-scripts`, behind a
|
|
136
|
+
registry mirror and offline. Everything but `cargo install` ships a prebuilt executable.
|
|
133
137
|
|
|
134
138
|
npm delivers it the way esbuild and Biome do: one small `dev-prune` package that lists
|
|
135
139
|
seven platform packages as optional dependencies, of which npm installs exactly the one
|
|
@@ -137,8 +141,14 @@ matching your machine. That is why there is no download step to block. Windows w
|
|
|
137
141
|
1.8.0 onwards — earlier versions installed and then reported no binary to run, so a
|
|
138
142
|
machine still holding `dev-prune@1.7.0` needs `npm install -g dev-prune@latest`.
|
|
139
143
|
|
|
140
|
-
|
|
141
|
-
|
|
144
|
+
bun, pnpm and Yarn install that same package, and dev-prune treats each as a channel of
|
|
145
|
+
its own rather than as npm: a copy `bun add -g` put there is upgraded and removed with
|
|
146
|
+
bun. Running npm against it would install a *second* copy under npm's prefix and leave
|
|
147
|
+
bun's, still on `PATH`, at the old version. `devp update --channels` prints every
|
|
148
|
+
channel's upgrade command if you want to see the whole table.
|
|
149
|
+
|
|
150
|
+
[crates.io](https://crates.io/crates/dev-prune) stores source and nothing else, so
|
|
151
|
+
`cargo install` has no binary to fetch and always compiles. [`cargo binstall`](https://github.com/cargo-bins/cargo-binstall) is the
|
|
142
152
|
one that downloads: `Cargo.toml` tells it where this project's release archives live, so
|
|
143
153
|
it unpacks the same executable the installers use, with no toolchain involved.
|
|
144
154
|
|
|
@@ -214,6 +224,18 @@ rules file that editor actually reads — `.github/copilot-instructions.md`, `.c
|
|
|
214
224
|
`CLAUDE.md`, `.junie/guidelines.md` and the rest — so an agent working in the repository
|
|
215
225
|
knows what dev-prune will and will not delete before it suggests anything.
|
|
216
226
|
|
|
227
|
+
**Claude Code can go first**, before `devp` exists on the machine at all — this
|
|
228
|
+
repository is also a Claude Code plugin marketplace:
|
|
229
|
+
|
|
230
|
+
```text
|
|
231
|
+
/plugin marketplace add Life-Experimentalist/dev-prune
|
|
232
|
+
/plugin install dev-prune@dev-prune
|
|
233
|
+
```
|
|
234
|
+
|
|
235
|
+
One skill, no hooks and no MCP server, and it is the same `SKILL.md` the binary embeds.
|
|
236
|
+
That is the useful order for an agent: read what dev-prune does and refuses to do, then
|
|
237
|
+
install it.
|
|
238
|
+
|
|
217
239
|
Everything about editors, in one place:
|
|
218
240
|
[docs/IDE_INTEGRATION.md](docs/IDE_INTEGRATION.md).
|
|
219
241
|
|
|
@@ -270,6 +292,39 @@ Every install channel in detail: [docs/DISTRIBUTION.md](docs/DISTRIBUTION.md).
|
|
|
270
292
|
> terminal and a scheduled task alike — with no profile to re-source, and no chance of an
|
|
271
293
|
> upgrade leaving `devp` on the old version.
|
|
272
294
|
|
|
295
|
+
### Every place it is published
|
|
296
|
+
|
|
297
|
+
Nine channels, one project. The middle column is the **exact** string each registry
|
|
298
|
+
answers to — names this close together are how a typo becomes somebody else's package,
|
|
299
|
+
so they are worth copying rather than typing.
|
|
300
|
+
|
|
301
|
+
| Where | Published as | What you get |
|
|
302
|
+
|---|---|---|
|
|
303
|
+
| [crates.io](https://crates.io/crates/dev-prune) | **`dev-prune`** | Source. `cargo install` compiles it; `cargo binstall` fetches the release archive instead. |
|
|
304
|
+
| [PyPI](https://pypi.org/project/dev-prune/) | **`dev-prune`** | Six wheels, each containing the binary. `pip`, `pipx`, `uv tool`. |
|
|
305
|
+
| [npm](https://www.npmjs.com/package/dev-prune) | **`dev-prune`** | A dispatcher plus seven platform packages; npm installs the one matching your machine. |
|
|
306
|
+
| [GitHub Releases](https://github.com/Life-Experimentalist/dev-prune/releases) | `dev-prune-v<ver>-<platform>` | Seven checksummed, provenance-attested archives. What the install scripts fetch. |
|
|
307
|
+
| [Homebrew](https://github.com/Life-Experimentalist/homebrew-tap) | **`Life-Experimentalist/tap`** | A one-formula tap, so `brew upgrade` keeps finding new versions. |
|
|
308
|
+
| [Scoop](https://github.com/Life-Experimentalist/scoop-bucket) | **`life-experimentalist`** | A one-manifest bucket, for the same reason. |
|
|
309
|
+
| [VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=VKrishna04.dev-prune) | **`VKrishna04.dev-prune`** | The editor extension. VS Code and the forks on Microsoft's gallery. |
|
|
310
|
+
| [Open VSX](https://open-vsx.org/extension/VKrishna04/dev-prune) | **`VKrishna04.dev-prune`** | The same extension, for VSCodium, Cursor, Windsurf, Positron and Kiro. |
|
|
311
|
+
| [SchemaStore](https://www.schemastore.org/) | **`.devprune.json`** | The config schema, by filename. No extension and no `$schema` key needed. |
|
|
312
|
+
|
|
313
|
+
[WinGet](https://github.com/microsoft/winget-pkgs/pull/422809) is submitted and in
|
|
314
|
+
review. It is not in the table because it does not resolve yet.
|
|
315
|
+
|
|
316
|
+
Two of those rows are not installs of dev-prune at all. SchemaStore is why JetBrains
|
|
317
|
+
IDEs, Visual Studio, Neovim and Zed validate `.devprune.json` with nothing installed —
|
|
318
|
+
the catalog entry points at a schema this repository hosts. And the editor extension is
|
|
319
|
+
a separate product with a separate version number, released on its own `vscode-v*` tags,
|
|
320
|
+
which is why the release marked *latest* on GitHub is always the CLI.
|
|
321
|
+
|
|
322
|
+
Anything calling itself dev-prune from anywhere other than these was not published by
|
|
323
|
+
its author. `devp doctor` names the channel the running copy came from, and every
|
|
324
|
+
release archive carries [GitHub build provenance](docs/RELEASING.md) that
|
|
325
|
+
`gh attestation verify` checks against this repository — a checksum only proves a file
|
|
326
|
+
arrived intact, which a substituted pair also does.
|
|
327
|
+
|
|
273
328
|
---
|
|
274
329
|
|
|
275
330
|
## 60-second tour
|
|
@@ -540,8 +595,8 @@ process that leaves a dirty working tree is a surprise.
|
|
|
540
595
|
| 🤖 **Self-installing automation** | OS-native scheduler (Task Scheduler, LaunchAgent, systemd user timer) and non-blocking Git hooks, installed at install time and restored after an upgrade. `auto_setup`, `auto_hooks`, `auto_daemon` or `DEV_PRUNE_NO_AUTO_SETUP=1` turn it off |
|
|
541
596
|
| ⚡ **0ms opt-out** | An `ignore.devprune.json` in a repository root is honoured by file presence alone — no read, no parse |
|
|
542
597
|
| 🔌 **`--json` on every reporting command** | `run`, `status`, `stats`, `trust` and `caches` each emit one versioned document on stdout, diagnostics on stderr. Built for scripts and agents |
|
|
543
|
-
| 🧠 **AI agent skill** | A token-lean `SKILL.md` embedded in the binary; `devp skill` exports it and prints onboarding prompts for Claude Code, Gemini Antigravity, Cursor, Windsurf, Copilot and OpenClaw |
|
|
544
|
-
| 🧰 **Editor extension** | Validates `.devprune.json` as you type and shows the workspace's reclaimable size in the status bar. `devp setup` offers to install it — once, only at a terminal — into VS Code, VSCodium, Cursor, Windsurf, Positron or Kiro, each from its own registry
|
|
598
|
+
| 🧠 **AI agent skill** | A token-lean `SKILL.md` embedded in the binary; `devp skill` exports it and prints onboarding prompts for Claude Code, Gemini Antigravity, Cursor, Windsurf, Copilot and OpenClaw, and the repository doubles as a Claude Code plugin marketplace |
|
|
599
|
+
| 🧰 **Editor extension** | Validates `.devprune.json` as you type and shows the workspace's reclaimable size in the status bar. `devp setup` offers to install it — once, only at a terminal — into VS Code, VSCodium, Cursor, Windsurf, Positron or Kiro, each from its own registry, falling back to the `.vsix` from the extension's own release. [docs/IDE_INTEGRATION.md](docs/IDE_INTEGRATION.md) |
|
|
545
600
|
| 🖼️ **File manager icons** | `devp icon` registers `*.devprune.json` with the OS file manager — a real `shared-mime-info` type plus hicolor icons on Linux, a folder icon on Windows. It never edits your editor settings, `PATH` or shell startup files |
|
|
546
601
|
| 🌏 **Unicode-safe paths** | A repository at `ワークスペース/项目目录名称测试/프론트엔드` scans, verifies, prunes and restores exactly like an ASCII one, on all three platforms. Terminal tables are padded by display *column*, not by character, so full-width CJK names keep `devp status` and `devp doctor` aligned. Accented Latin, Cyrillic, Arabic and emoji directory names too |
|
|
547
602
|
| 🚫 **No telemetry** | One optional unauthenticated `GET` to GitHub's public releases endpoint, at most weekly, no body and no identifier. Nothing else leaves the machine |
|
|
@@ -729,30 +784,159 @@ Global settings live in `%APPDATA%\dev-prune` (Windows),
|
|
|
729
784
|
once on a first install — so the defaults are something you agreed to rather than
|
|
730
785
|
inherited — and again after an upgrade adds a setting you have never been shown.
|
|
731
786
|
|
|
732
|
-
|
|
733
|
-
|
|
734
|
-
|
|
735
|
-
|
|
736
|
-
|
|
737
|
-
|
|
738
|
-
|
|
739
|
-
|
|
740
|
-
|
|
741
|
-
|
|
742
|
-
|
|
743
|
-
|
|
744
|
-
|
|
|
745
|
-
|
|
|
746
|
-
| `
|
|
747
|
-
|
|
748
|
-
|
|
787
|
+
If you already know what you want, `devp config recommended` is the one-command version:
|
|
788
|
+
it turns on the eight adapters and build trees that are off by default because they are
|
|
789
|
+
not universally wanted, and leaves `allow_manifest_rewrite` — the one recommendation
|
|
790
|
+
that edits files Git tracks — named, explained and off unless you add
|
|
791
|
+
`--with-cautious`. `devp config show` lists whatever you have not taken yet.
|
|
792
|
+
|
|
793
|
+
Thirty settings, in the seven groups the configurator asks them in — the order the
|
|
794
|
+
decisions actually arrive in. Every key, with its full description and range, is in the
|
|
795
|
+
[CLI reference](docs/CLI_REFERENCE.md#8-devp-config-action).
|
|
796
|
+
|
|
797
|
+
**The language this is all in** — what dev-prune prints its own headings in.
|
|
798
|
+
|
|
799
|
+
| Key | Default | Meaning |
|
|
800
|
+
| :--- | :---: | :--- |
|
|
801
|
+
| `language` | `en` | One of twelve catalogues — `en`, `zh`, `hi`, `te`, `ta`, `kn`, `ml`, `bn`, `mr`, `gu`, `pa`, `sa`. Only dev-prune's own headings and summary lines move; `--json`, exit codes, flag names, config keys and adapter names are English in every one, so nothing a script reads changes. `DEV_PRUNE_LANG` overrides it for one command. See [TRANSLATIONS.md](docs/TRANSLATIONS.md) |
|
|
802
|
+
|
|
803
|
+
**What gets pruned** — the size and age of what a pass considers at all.
|
|
804
|
+
|
|
805
|
+
| Key | Default | Meaning |
|
|
806
|
+
| :--- | :---: | :--- |
|
|
807
|
+
| `idle_days` | `15` | How long a repository must be untouched to become a candidate |
|
|
808
|
+
| `min_size_mb` | `0` | Smallest bloat directory worth deleting; `0` disables the floor |
|
|
809
|
+
| `scan_depth` | `6` | Levels below a repository root that discovery descends |
|
|
810
|
+
| `disabled_adapters` | *(none)* | Adapters to leave alone entirely, by name — as if that ecosystem were not installed |
|
|
811
|
+
| `adapter_idle_days` | *(none)* | Per-adapter idle floors, as `cargo=90,npm=30` — each raises only its own window |
|
|
812
|
+
|
|
813
|
+
**Before anything is deleted** — what stands between a candidate and a deletion.
|
|
814
|
+
|
|
815
|
+
| Key | Default | Meaning |
|
|
816
|
+
| :--- | :---: | :--- |
|
|
817
|
+
| `require_confirmation` | `true` | Whether a pass asks before deleting |
|
|
818
|
+
| `allow_manifest_rewrite` | `false` | Whether verification may *repair* a drifted lockfile instead of refusing |
|
|
819
|
+
| `command_timeout_secs` | `600` | Ceiling on one package manager command; nothing compiles under it |
|
|
820
|
+
|
|
821
|
+
**Build trees — off by default**, because everything here comes back by recompiling
|
|
822
|
+
rather than downloading. That is the whole reason each one is a switch.
|
|
823
|
+
|
|
824
|
+
| Key | Default | Meaning |
|
|
825
|
+
| :--- | :---: | :--- |
|
|
826
|
+
| `enable_cargo` … `enable_cmake_build` | `false` | Turn on an opt-in build-tool adapter; `build_idle_days` (`45`) gates all eight |
|
|
827
|
+
|
|
828
|
+
**Shared download caches** — one key, because the cap only ever marks.
|
|
829
|
+
|
|
830
|
+
| Key | Default | Meaning |
|
|
831
|
+
| :--- | :---: | :--- |
|
|
832
|
+
| `cache_max_gb` | *(none)* | Per-manager cache caps in GiB, as `uv=10,npm=10` — the cap itself deletes nothing |
|
|
833
|
+
|
|
834
|
+
**Running without being asked** — what dev-prune may install here, and how often it may
|
|
835
|
+
act on its own.
|
|
836
|
+
|
|
837
|
+
| Key | Default | Meaning |
|
|
838
|
+
| :--- | :---: | :--- |
|
|
839
|
+
| `auto_setup` · `auto_daemon` · `auto_hooks` | `true` | Whether the integration pass may run unattended, and what it may install |
|
|
840
|
+
| `auto_config` | `false` | Whether `devp init` / `devp link` write a `.devprune.json` into newly registered repositories |
|
|
841
|
+
| `auto_hooks_chain` | `false` | Whether it may take a `core.hooksPath` another tool holds — off, it is not yours |
|
|
842
|
+
| `check_interval_days` | `2` | How often the OS scheduler runs a pass |
|
|
843
|
+
|
|
844
|
+
**Keeping dev-prune current** — whether this copy looks for a newer one, and may install it.
|
|
845
|
+
|
|
846
|
+
| Key | Default | Meaning |
|
|
847
|
+
| :--- | :---: | :--- |
|
|
848
|
+
| `update_check` | `true` | Whether the periodic release check runs |
|
|
849
|
+
| `update_check_interval_days` · `update_check_timeout_secs` | `7` · `5` | Minimum gap between checks, and how long one may hang |
|
|
850
|
+
| `auto_update` | `true` | Install a newer release at the end of a pass. Stands aside on WinGet, Scoop and Homebrew, where the manager owns the upgrade |
|
|
851
|
+
| `version_lock` | `false` | Pin this copy to the version it is. Nothing dev-prune does then replaces the binary, and there is no flag that bypasses it |
|
|
852
|
+
|
|
853
|
+
### Per-repository settings
|
|
749
854
|
|
|
750
855
|
Three of them — `idle_days` (as `override_idle_days`), `min_size_mb` and `scan_depth` —
|
|
751
|
-
also take a per-repository form
|
|
752
|
-
|
|
753
|
-
`.devprune.json`, and a repository you have never read should not be able to grant itself
|
|
856
|
+
also take a per-repository form, where they win for that tree only. The rest are
|
|
857
|
+
deliberately global: a repository you have never read should not be able to grant itself
|
|
754
858
|
permission to have its manifests rewritten during an unattended pass.
|
|
755
859
|
|
|
860
|
+
A repository can hold **two** config files, and the difference is who they are for.
|
|
861
|
+
|
|
862
|
+
| File | Committed? | For |
|
|
863
|
+
|---|---|---|
|
|
864
|
+
| `.devprune.json` | No — added to `.git/info/exclude` when written | Your copy of this one repository, on this one machine |
|
|
865
|
+
| `project.devprune.json` | **Yes** — `devp config project . --team` writes it to be staged | What the project decided, reaching a fresh clone by itself |
|
|
866
|
+
|
|
867
|
+
Where both exist, **every key the project file names wins**, and the personal file
|
|
868
|
+
answers everything it does not. That is the inverse of the usual "local overrides
|
|
869
|
+
global", and deliberately: a colleague's stale local answer should not quietly overrule
|
|
870
|
+
what the project decided, while a personal override still works on every setting the team
|
|
871
|
+
left open. "Names a key" means the key is literally in the file — a project file that
|
|
872
|
+
never mentions `ignore` does not un-ignore your repository, which is why it is created
|
|
873
|
+
holding nothing but its `$schema` line.
|
|
874
|
+
|
|
875
|
+
```mermaid
|
|
876
|
+
flowchart TD
|
|
877
|
+
Key["One setting, in one repository"] --> Shared{"Named in<br/>project.devprune.json?"}
|
|
878
|
+
Shared -->|Yes| WinShared["The team's value.<br/>Committed, so a fresh clone starts here."]
|
|
879
|
+
Shared -->|No| Personal{"Named in<br/>.devprune.json?"}
|
|
880
|
+
Personal -->|Yes| WinPersonal["Your value.<br/>Never committed, never in git status."]
|
|
881
|
+
Personal -->|No| Global["The global setting on this machine,<br/>or its default."]
|
|
882
|
+
```
|
|
883
|
+
|
|
884
|
+
Nothing dev-prune writes on its own touches the shared file. `devp link`,
|
|
885
|
+
`devp doctor --fix`, `devp config project . --update` and `[i]` in the dashboard all
|
|
886
|
+
write `.devprune.json`, so no routine action of yours turns into a change on a branch
|
|
887
|
+
your colleagues share; `--team` is the only way to write the other file, and you
|
|
888
|
+
have to type it. Run `devp config project .` in a repository that has both and it
|
|
889
|
+
prints which file each effective value came from.
|
|
890
|
+
|
|
891
|
+
### Directories only the project knows about
|
|
892
|
+
|
|
893
|
+
Every adapter earns its right to delete the same way: it finds a lockfile, verifies the
|
|
894
|
+
lockfile can rebuild what is about to go, and only then deletes. Some trees have no
|
|
895
|
+
lockfile and are still rebuildable — a generated fixture set, a vendored toolchain, a
|
|
896
|
+
cache with a `make` target behind it. A repository can name those itself, in either
|
|
897
|
+
config file:
|
|
898
|
+
|
|
899
|
+
```json
|
|
900
|
+
{
|
|
901
|
+
"prunable": {
|
|
902
|
+
"directories": [
|
|
903
|
+
{
|
|
904
|
+
"path": "tools/vendor",
|
|
905
|
+
"rebuild": "make vendor",
|
|
906
|
+
"why": "regenerated from tools/manifest.toml"
|
|
907
|
+
}
|
|
908
|
+
]
|
|
909
|
+
}
|
|
910
|
+
}
|
|
911
|
+
```
|
|
912
|
+
|
|
913
|
+
`rebuild` is required, and required is the point: an optional one would make "delete
|
|
914
|
+
this, I have no idea how to get it back" the easiest thing to write in a file that gets
|
|
915
|
+
committed and cloned. If a directory genuinely needs nothing to bring it back, say so
|
|
916
|
+
— `"rebuild": "echo not needed"` is a legal answer and works on every platform.
|
|
917
|
+
dev-prune shows the command; it never runs it.
|
|
918
|
+
|
|
919
|
+
Declared directories go through the ordinary pass under the adapter name `declared`, so
|
|
920
|
+
they are listed by `devp status`, obey `--dry-run`, `--min-size` and `--only`, and are
|
|
921
|
+
deleted by the scheduled run alongside everything else.
|
|
922
|
+
|
|
923
|
+
A declaration is a claim, not an instruction. `project.devprune.json` is committed, so a
|
|
924
|
+
repository you cloned can declare whatever it likes, and `devp run` may be running from a
|
|
925
|
+
scheduler with nobody watching. Before deleting one, dev-prune requires that:
|
|
926
|
+
|
|
927
|
+
- the path is relative, has no `..`, and is neither `.git` nor the repository root;
|
|
928
|
+
- it resolves to somewhere inside the repository, even through a symlinked parent;
|
|
929
|
+
- Git is tracking nothing inside it — a lockfile cannot rebuild a file that is in the
|
|
930
|
+
repository itself;
|
|
931
|
+
- the first word of `rebuild` is a program this machine actually has.
|
|
932
|
+
|
|
933
|
+
A claim that fails any of those is printed with the reason, and nothing is deleted.
|
|
934
|
+
|
|
935
|
+
This section is the one part of either file that does not follow the precedence above:
|
|
936
|
+
the two lists **add up**. A list is not a decision, so a team declaration never discards
|
|
937
|
+
one you wrote yourself, and naming the same path in both leaves one directory, rebuilt
|
|
938
|
+
by the committed command.
|
|
939
|
+
|
|
756
940
|
An out-of-range value is rejected with the range in the message rather than silently
|
|
757
941
|
clamped. `scan_depth` included: `config set` accepts `1`–`32` and refuses anything else
|
|
758
942
|
outright — the clamp to that range survives only as the backstop for a hand-edited
|
|
@@ -815,7 +999,7 @@ flowchart TD
|
|
|
815
999
|
|
|
816
1000
|
Engine --> FastIgnore{ignore.devprune.json?}
|
|
817
1001
|
FastIgnore -->|Exists| Skip["Skip Repo O(1) 0ms"]
|
|
818
|
-
FastIgnore -->|Missing| PerRepoConfig["Read .devprune.json"]
|
|
1002
|
+
FastIgnore -->|Missing| PerRepoConfig["Read project.devprune.json,<br/>then .devprune.json"]
|
|
819
1003
|
|
|
820
1004
|
PerRepoConfig --> GitScanner["Git Scanner & Activity Solver<br/>(.git commits + mtime fallback)"]
|
|
821
1005
|
Engine --> PreCheck["Required Ecosystem Binary Pre-Checker"]
|
package/bin/dev-prune
CHANGED
|
Binary file
|
package/package.json
CHANGED