Repository navigation
fix: never install into a version-managed npm prefix - #98
Merged
Merged
Conversation
npm prefix -g under mise/nvm/asdf/volta/fnm points inside the version-managed node install, and npm globals there vanish when the manager switches or upgrades node (exactly what happened on this machine: the one-liner installed the fork into mise's node 26.2.0 dir). Those prefixes are now skipped and ~/.local wins; PI_INSTALL_PREFIX still overrides. End-to-end verified: the plain one-liner now lands in ~/.local/bin/pi.
R-Dson
added a commit
that referenced
this pull request
Aug 31, 2026
install.sh: preflight checks (curl, npm, Node >= 22.19), install-prefix selection (npm global prefix or ~/.local, PI_INSTALL_PREFIX override), downgrade warning, foreign-binary guard, refusal to install into a version-managed npm prefix, pinned or latest tarball fetch, npm install -g --ignore-scripts, post-install PATH note, and --uninstall.
R-Dson
added a commit
that referenced
this pull request
Aug 31, 2026
install.sh: preflight checks (curl, npm, Node >= 22.19), install-prefix selection (npm global prefix or ~/.local, PI_INSTALL_PREFIX override), downgrade warning, foreign-binary guard, refusal to install into a version-managed npm prefix, pinned or latest tarball fetch, npm install -g --ignore-scripts, post-install PATH note, and --uninstall.
R-Dson
added a commit
that referenced
this pull request
Sep 4, 2026
Adds missing entries the audit found: the fork installer pipeline (#97/#98), the musl fd/rg Linux bootstrap fix (earendil-works#9070), and the signal-killed exit-code fix (earendil-works#8994, agent + coding-agent). Duplicates the user-facing ai/agent changes into the coding-agent changelog per the /cl cross-package rule: per-turn Anthropic effort persistence, the xhigh thinking-level cluster (#124/#139), the timeoutMs deadline leak (#139), proxied thinking-level persistence, and the provider-fix round (earendil-works#9021/earendil-works#8961/earendil-works#9047).
R-Dson
added a commit
that referenced
this pull request
Sep 4, 2026
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.
Follow-up to #97, found by running the one-liner on a mise machine:
npm prefix -gpointed inside mise's node 26.2.0 install, so the fork landed in~/.local/share/mise/installs/node/26.2.0/bin/pi— a directory that stops existing the moment mise upgrades node, orphaning the install (and it shadowed the stable~/.local/bin/picopy).Fix: the prefix selection now skips version-managed npm prefixes (
mise,nvm,asdf,volta,fnm) and falls through to~/.local, with the existing "Using install prefix" line making the choice visible.PI_INSTALL_PREFIXstill overrides for anyone who genuinely wants a managed prefix.End-to-end verified on this machine: the plain one-liner now installs to
~/.local/bin/piandpireports0.84.4-fork.4. The stray install and mise's upstream pi copy were removed (onepion PATH total).