Skip to content

Commit e5e2d18

Browse files
hyperpolymathclaude
andcommitted
chore(mise): remove 13 phantom tools and a no-op [alias] block
mise.toml named 13 tools absent from the mise registry (denojs, pip, cargo, go-task, gofmt, isort, git, gnu-sed, gnu-grep, gnu-tar, vitest, pytest, jest), so mise emitted ~25 warning lines per shell entry while installing none of them. The [alias] block was dead: mise's [alias] maps an alias to a TOOL PLUGIN, it does not define tasks, so build/test/lint/fmt never ran. go-task is dropped rather than renamed: the bare name `task` does not resolve either, despite `mise registry` listing it as aqua:go-task/task. Listing is not resolution — verified with `mise ls-remote`. Verified after `mise trust` (an untrusted mise.toml is silently ignored, so zero warnings from an untrusted file proves nothing): 0 warnings and 0 errors attributable to this file. Introduced by sweep2 (2026-07-18); this is one of 56 repos that committed the broken file (417 identical copies existed estate-wide, most only in uncommitted local working trees). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
1 parent 1791bbc commit e5e2d18

1 file changed

Lines changed: 53 additions & 26 deletions

File tree

mise.toml

Lines changed: 53 additions & 26 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,8 @@
1+
# Every tool name below was checked against `mise registry` AND resolved with
2+
# `mise ls-remote` before being written. The previous version of this file named
3+
# 13 tools that do not exist in the registry, so mise emitted ~25 lines of
4+
# warnings on every shell entry while installing none of them.
5+
16
[tools]
27
# Language runtimes
38
node = "latest"
@@ -7,20 +12,16 @@ go = "latest"
712
zig = "latest"
813
java = "latest"
914
bun = "latest"
10-
denojs = "latest"
15+
deno = "latest" # was `denojs` — not a registry name
1116

12-
# Package managers
17+
# Package managers / task runner
1318
npm = "latest"
1419
yarn = "latest"
1520
pnpm = "latest"
16-
pip = "latest"
17-
cargo = "latest"
18-
go-task = "latest"
21+
just = "latest" # the estate's task runner (Justfile)
1922

20-
# Formatting & Linting
21-
gofmt = "latest"
23+
# Formatting & linting
2224
black = "latest"
23-
isort = "latest"
2425
ruff = "latest"
2526
prettier = "latest"
2627
shfmt = "latest"
@@ -31,27 +32,53 @@ cmake = "latest"
3132
make = "latest"
3233
ninja = "latest"
3334

34-
# Shell tools
35-
git = "latest"
36-
gnu-sed = "latest"
37-
gnu-tar = "latest"
38-
gnu-grep = "latest"
39-
40-
# Testing
41-
vitest = "latest"
42-
pytest = "latest"
43-
jest = "latest"
35+
# ---------------------------------------------------------------------------
36+
# REMOVED — none of these resolve in the mise registry, so they installed
37+
# nothing and only produced warnings. Grouped by why they were wrong:
38+
#
39+
# Already provided by a tool that IS listed above:
40+
# cargo -> ships with `rust`
41+
# gofmt -> ships with `go`
42+
# pip -> ships with `python`
43+
#
44+
# Project-level dependencies, not system tools. These belong in
45+
# package.json / pyproject.toml / mix.exs, not in a toolchain manager:
46+
# vitest, jest, pytest, isort
47+
#
48+
# Base system binaries that mise should not be shadowing on Linux:
49+
# git, gnu-sed, gnu-grep, gnu-tar
50+
# (If a GNU-vs-BSD coreutils difference ever actually bites on macOS, add
51+
# `coreutils`, which does exist in the registry, rather than these names.)
52+
#
53+
# Task runner that never installed:
54+
# go-task -> not a registry name. NB the bare name `task` does not work
55+
# either: `mise registry` LISTS it as `aqua:go-task/task`, but resolving
56+
# `task@latest` still fails. Appearing in `mise registry` output is NOT
57+
# sufficient to conclude a name resolves — check with `mise ls-remote`.
58+
# `just` is listed above instead.
59+
# ---------------------------------------------------------------------------
4460

4561
[env]
46-
# Common environment variables
4762
NODE_ENV = "development"
4863
PYTHONDONTWRITEBYTECODE = "1"
4964
PYTHONUNBUFFERED = "1"
5065

51-
# Task runner alias
52-
[alias]
53-
task = "go-task"
54-
build = "cargo build --release || npm run build || go build"
55-
test = "cargo test || npm test || go test ./..."
56-
lint = "ruff check . || prettier --check . || black --check ."
57-
fmt = "ruff format . || prettier --write . || black ."
66+
# ---------------------------------------------------------------------------
67+
# REMOVED — an `[alias]` section holding what were clearly meant to be tasks:
68+
#
69+
# [alias]
70+
# task = "go-task"
71+
# build = "cargo build --release || npm run build || go build"
72+
# test = "cargo test || npm test || go test ./..."
73+
# lint = "ruff check . || prettier --check . || black --check ."
74+
# fmt = "ruff format . || prettier --write . || black ."
75+
#
76+
# mise's `[alias]` maps an alias to a TOOL PLUGIN — it does not define tasks,
77+
# so none of these ever ran. mise also warns that `[alias]` is deprecated in
78+
# favour of `[tool_alias]`.
79+
#
80+
# They are not re-added as `[tasks]`: the estate drives builds through the
81+
# Justfile, and a second task runner sharing the verbs `build`/`test`/`lint`/
82+
# `fmt` — one of which silently falls through `||` chains into a different
83+
# language's build — is worse than one. Use `just <recipe>`.
84+
# ---------------------------------------------------------------------------

0 commit comments

Comments
 (0)