deprecated-tracker 2.2.0 → 2.3.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/CHANGELOG.md +10 -0
- package/README.md +1 -1
- package/docs/CLI.md +5 -1
- package/out/cli.js +74 -71
- package/package.json +211 -211
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,16 @@
|
|
|
2
2
|
|
|
3
3
|
All notable changes to the "Deprecated Tracker" extension will be documented in this file.
|
|
4
4
|
|
|
5
|
+
## [2.3.0]
|
|
6
|
+
|
|
7
|
+
### Changed
|
|
8
|
+
|
|
9
|
+
- **The bare `deprecated-tracker` now prints its help instead of scanning the working directory.** Typing the name to find out what a freshly installed tool does answered "0 item(s) — PASS" from whatever directory the shell was in, which reads like the scanner is broken. Ask for the current directory explicitly: `deprecated-tracker .`. Every invocation that already carries a path or a flag is unaffected, including `--update-baseline`, `--staged`, `--changed` and `--files`.
|
|
10
|
+
|
|
11
|
+
### Fixed
|
|
12
|
+
|
|
13
|
+
- **`mcp install` never used the agent's own CLI on Windows.** `claude` and `codex` are `.cmd` shims there, and Node refuses to `execFile` a `.cmd` without a shell (CVE-2024-27980) — the bare name failed with `ENOENT` and the shim with `EINVAL`, so every Windows machine silently fell through to the config-file writer. That path works, but for `--scope user` it rewrites the whole of `~/.claude.json`, reformatting preferences that have nothing to do with this tool.
|
|
14
|
+
|
|
5
15
|
## [2.2.0]
|
|
6
16
|
|
|
7
17
|
### Added
|
package/README.md
CHANGED
|
@@ -16,7 +16,7 @@ Failing a build on *any* deprecated code is useless once a codebase already has
|
|
|
16
16
|
|
|
17
17
|
```bash
|
|
18
18
|
npx deprecated-tracker --update-baseline # commit .deprecated-tracker-baseline.json
|
|
19
|
-
npx deprecated-tracker
|
|
19
|
+
npx deprecated-tracker . # exits 1 only if the count went up
|
|
20
20
|
```
|
|
21
21
|
|
|
22
22
|
A first run with no baseline **passes** and tells you to record one. When the count falls it passes and prints how stale the baseline has become.
|
package/docs/CLI.md
CHANGED
|
@@ -12,9 +12,13 @@ The `deprecated-tracker` CLI does the other thing: it records today's count as a
|
|
|
12
12
|
```bash
|
|
13
13
|
npm run build # produces out/cli.js
|
|
14
14
|
node bin/deprecated-tracker.js --update-baseline # commit the baseline file
|
|
15
|
-
node bin/deprecated-tracker.js
|
|
15
|
+
node bin/deprecated-tracker.js . # exits 1 only if the count went up
|
|
16
16
|
```
|
|
17
17
|
|
|
18
|
+
A scan needs a path or a flag; the bare name prints the help instead, so
|
|
19
|
+
someone who types it to see what it does does not get a scan of whatever
|
|
20
|
+
directory their shell was in.
|
|
21
|
+
|
|
18
22
|
| Option | Effect |
|
|
19
23
|
|---|---|
|
|
20
24
|
| `--files <file...>` | Scan only these files; everything after is a path |
|