Skip to content

fix: point init_node PATH at $PNPM_HOME/bin#53

Merged
bushidocodes merged 1 commit into
masterfrom
fix/init-node-pnpm-bin
Jun 16, 2026
Merged

fix: point init_node PATH at $PNPM_HOME/bin#53
bushidocodes merged 1 commit into
masterfrom
fix/init-node-pnpm-bin

Conversation

@bushidocodes

Copy link
Copy Markdown
Owner

Problem

init_node added $PNPM_HOME to PATH:

export PNPM_HOME="$HOME/.local/share/pnpm"
export PATH="$PNPM_HOME:$PATH"

But pnpm v11 installs its binary and all global tools into $PNPM_HOME/bin. So after a successful install, a login shell's PATH had the wrong dir and none of pnpm/node/bats/http-server/netlify/fkill were on PATH despite installing correctly (binaries confirmed in ~/.local/share/pnpm/bin/). This is the shell-side counterpart to the Makefile fix in #48.

Fix

export PATH="$PNPM_HOME/bin:$PATH"

Matches what pnpm's own installer writes to ~/.bashrc. Found by re-running install.sh in a fresh ubuntu:24.04 container.

Fixes #52

🤖 Generated with Claude Code

pnpm v11 installs its binary and global tools into $PNPM_HOME/bin, but
init_node added $PNPM_HOME to PATH, so pnpm/node/bats/http-server/
netlify/fkill were never on PATH in a shell despite installing
correctly. Use $PNPM_HOME/bin, matching what pnpm's own installer
writes to ~/.bashrc. Shell-side counterpart to the Makefile fix in #48.

Found by re-running install.sh in a fresh ubuntu:24.04 container.

Fixes #52

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@bushidocodes bushidocodes merged commit 9c6c107 into master Jun 16, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

init_node puts wrong dir on PATH: pnpm v11 binaries live in $PNPM_HOME/bin

1 participant