dreampiler/kandev
1
0
Fork 0
Code Issues 43 Pull Requests Actions 6 Packages Projects Releases Wiki Activity

fix: preserve nvm node path in service installs (#1527)

Browse Source
This commit is contained in:
Carlos Florêncio
2026-06-29 08:46:02 +01:00
committed by GitHub
parent 9fb48224f2
commit 7205998fc8
4 changed files with 322 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/run-as-a-service.md
+3 -1
View File
@@ -127,7 +127,9 @@ If you'd rather not deal with linger and you're already comfortable with sudo, i
## What's Inside the Unit File
The unit hard-codes absolute paths so it works in the empty `PATH` that systemd/launchd give a fresh service. A typical Linux user unit looks like:
The unit hard-codes absolute paths so it works in the empty `PATH` that systemd/launchd give a fresh service. When Node tooling is installed through a per-user manager such as nvm, fnm, asdf, Volta, or mise, `kandev service install` also bakes the detected `node`/`npm`/`npx` bin directory into `PATH`; re-run the install command after changing the active Node version. For fnm, the installer resolves multishell symlinks when possible so the unit records the stable Node installation path instead of the temporary multishell directory. If the service file still points at a stale fnm multishell path, re-run `kandev service install` from a shell where `node`, `npm`, and `npx` resolve through valid symlinks. For `--system` installs, some `sudo` configurations reset `PATH` with `secure_path`; run the install command from an environment where `node`, `npm`, and `npx` still resolve, or put stable symlinks in the run-as user's `~/.local/bin`.
A typical Linux user unit looks like:
```ini
# managed by kandev — regenerated by `kandev service install`