fix: let aube's preinstall run under mise's new npm backend - #22
Open
natevick wants to merge 1 commit into
Open
Conversation
mise 2026.8.5 changed the npm backend: it now resolves and links packages itself instead of shelling out to npm, and it passes --ignore-scripts. @endevco/aube ships no bin/ -- its "preinstall" runs installArchSpecificPackage.js, which downloads the ~48M arch-specific binary. With scripts skipped, mise installed a package with no executable, recorded backend metadata saying so, and dropped the aube / aubr / aubx shims entirely. `aube` became command-not-found. Both settings are required; verified by removing each in turn: - shell_out = true alone: npm runs but still with --ignore-scripts, and mise warns it skipped the preinstall. - npm_args alone (shell_out = false): mise's internal installer ignores it and the binary is never fetched. Together: install is clean, `aube --version` and `aubx --version` both report 1.38.1 through the shims. shell_out = true does reintroduce npm subprocesses, which is the surface the 2026-08-12 fork bomb recursed through. That is acceptable only because the box now runs mise 2026.8.5, which includes jdx/mise#8475 (shims stripped from dependency_env PATH). Do not set this on a mise older than 2026.8.2. Lives here rather than machine-local ~/.config/mise/config.toml so a fresh machine reproduces a working aube. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01ARNZyPcAj3K2LhupCDn5gQ
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
aubewas silently broken by upgrading mise 2026.2.17 → 2026.8.5. New mise resolves/links npm packages itself rather than shelling out, and passes--ignore-scripts.@endevco/aubeships nobin/— itspreinstallrunsinstallArchSpecificPackage.jsto download the ~48M arch-specific binary. Scripts skipped ⇒ package with no executable, backend metadata recorded as such, and theaube/aubr/aubxshims dropped.aubebecame command-not-found.Both settings are required — verified by removing each in turn
shell_out = trueonly--ignore-scripts; mise warns it skippedpreinstallnpm_argsonly (shell_out = false)aube --versionandaubx --versionreport 1.38.1 via shimsTrade-off, stated plainly
shell_out = truereintroduces npm subprocesses — the surface the 2026-08-12 fork bomb recursed through. That is acceptable only because this box now runs mise 2026.8.5, which contains jdx/mise#8475 (shims stripped fromdependency_envPATH). Do not set this on mise older than 2026.8.2, whichinstall-mise.shalready enforces as the floor.Placed in the managed config rather than machine-local
~/.config/mise/config.tomlso a fresh machine reproduces a working aube.What this does not establish
Only tested on Linux/x86_64 with npm 10.9.8.
allow_builds(npm ≥ 11.16.0) would be the narrower opt-in — it scopes script execution to named packages instead of enabling it for every npm-backend tool — and is worth revisiting when npm crosses that version.