Final rebrand: rename remaining Rust source file to complete the gsd → forge transition. All parser references already use forge_parser after earlier commits. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
1.9 KiB
Pinning Node.js LTS on macOS with Homebrew
If you installed Node.js via Homebrew (brew install node), you're tracking the latest current release — which can include odd-numbered development versions (e.g. 23.x, 25.x). These aren't LTS and may have breaking changes or instability.
SF requires Node.js v22 or later and works best on an LTS (even-numbered) release. This guide shows how to pin Node 24 LTS using Homebrew.
Check your current version
node --version
If this shows an odd number (e.g. v23.x, v25.x), you're on a development release.
Install Node 24 LTS
Homebrew provides versioned formulas for LTS releases:
# Unlink the current (possibly non-LTS) version
brew unlink node
# Install Node 24 LTS
brew install node@24
# Link it as the default
brew link --overwrite node@24
Verify:
node --version
# Should show v24.x.x
Why pin to LTS?
- Stability — LTS releases receive bug fixes and security patches for 30 months
- Compatibility — npm packages (including SF) test against LTS versions
- No surprises —
brew upgradewon't jump you to an unstable development release
Prevent accidental upgrades
By default, brew upgrade will upgrade all packages, which could move you off the pinned version. Pin the formula:
brew pin node@24
To unpin later:
brew unpin node@24
Switching between versions
If you need multiple Node versions (e.g. 22 and 24), consider using a version manager instead:
- nvm —
nvm install 24 && nvm use 24 - fnm —
fnm install 24 && fnm use 24(faster, Rust-based) - mise —
mise use node@24(polyglot version manager)
These let you set per-project Node versions via .node-version or .nvmrc files.
Verify SF works
After pinning:
node --version # v24.x.x
npm install -g sf-run
sf --version