-
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathmise.toml
More file actions
84 lines (77 loc) · 3.12 KB
/
Copy pathmise.toml
File metadata and controls
84 lines (77 loc) · 3.12 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
# Every tool name below was checked against `mise registry` AND resolved with
# `mise ls-remote` before being written. The previous version of this file named
# 13 tools that do not exist in the registry, so mise emitted ~25 lines of
# warnings on every shell entry while installing none of them.
[tools]
# Language runtimes
node = "latest"
python = "latest"
rust = "latest"
go = "latest"
zig = "latest"
java = "latest"
bun = "latest"
deno = "latest" # was `denojs` — not a registry name
# Package managers / task runner
npm = "latest"
yarn = "latest"
pnpm = "latest"
just = "latest" # the estate's task runner (Justfile)
# Formatting & linting
black = "latest"
ruff = "latest"
prettier = "latest"
shfmt = "latest"
stylua = "latest"
# Build tools
cmake = "latest"
make = "latest"
ninja = "latest"
# ---------------------------------------------------------------------------
# REMOVED — none of these resolve in the mise registry, so they installed
# nothing and only produced warnings. Grouped by why they were wrong:
#
# Already provided by a tool that IS listed above:
# cargo -> ships with `rust`
# gofmt -> ships with `go`
# pip -> ships with `python`
#
# Project-level dependencies, not system tools. These belong in
# package.json / pyproject.toml / mix.exs, not in a toolchain manager:
# vitest, jest, pytest, isort
#
# Base system binaries that mise should not be shadowing on Linux:
# git, gnu-sed, gnu-grep, gnu-tar
# (If a GNU-vs-BSD coreutils difference ever actually bites on macOS, add
# `coreutils`, which does exist in the registry, rather than these names.)
#
# Task runner that never installed:
# go-task -> not a registry name. NB the bare name `task` does not work
# either: `mise registry` LISTS it as `aqua:go-task/task`, but resolving
# `task@latest` still fails. Appearing in `mise registry` output is NOT
# sufficient to conclude a name resolves — check with `mise ls-remote`.
# `just` is listed above instead.
# ---------------------------------------------------------------------------
[env]
NODE_ENV = "development"
PYTHONDONTWRITEBYTECODE = "1"
PYTHONUNBUFFERED = "1"
# ---------------------------------------------------------------------------
# REMOVED — an `[alias]` section holding what were clearly meant to be tasks:
#
# [alias]
# task = "go-task"
# build = "cargo build --release || npm run build || go build"
# test = "cargo test || npm test || go test ./..."
# lint = "ruff check . || prettier --check . || black --check ."
# fmt = "ruff format . || prettier --write . || black ."
#
# mise's `[alias]` maps an alias to a TOOL PLUGIN — it does not define tasks,
# so none of these ever ran. mise also warns that `[alias]` is deprecated in
# favour of `[tool_alias]`.
#
# They are not re-added as `[tasks]`: the estate drives builds through the
# Justfile, and a second task runner sharing the verbs `build`/`test`/`lint`/
# `fmt` — one of which silently falls through `||` chains into a different
# language's build — is worse than one. Use `just <recipe>`.
# ---------------------------------------------------------------------------