The comment said the bootstrapped-node candidate 'is first'; it is inserted second, after MOSAIC_RUNTIME_BIN. The ordering itself is correct — an explicit override should outrank a bootstrap — so this is a wording defect in a load-bearing comment, not a behaviour change. No executable line is touched. Found in review by mos-claude (review 166).
This commit is contained in:
@@ -272,8 +272,9 @@ _build_runtime_bin_prefix() {
|
|||||||
# records it in ~/.profile. The fleet unit runs `env -i ... bash --noprofile --norc`
|
# records it in ~/.profile. The fleet unit runs `env -i ... bash --noprofile --norc`
|
||||||
# by design, so ~/.profile is never read and the directory has to be named here.
|
# by design, so ~/.profile is never read and the directory has to be named here.
|
||||||
# The npm probe below cannot cover this: it reports a package prefix
|
# The npm probe below cannot cover this: it reports a package prefix
|
||||||
# (~/.npm-global), never a Node runtime directory. It is first so the bootstrapped
|
# (~/.npm-global), never a Node runtime directory. It sits ahead of the npm probe so
|
||||||
# runtime wins on a host that has both — that is the one the installer verified.
|
# the bootstrapped runtime wins on a host that has both — that is the one the installer
|
||||||
|
# verified — while an explicit MOSAIC_RUNTIME_BIN still outranks it.
|
||||||
# Runtime binaries are `#!/usr/bin/env node`, so without this the pane resolves the
|
# Runtime binaries are `#!/usr/bin/env node`, so without this the pane resolves the
|
||||||
# binary and then dies on `env: 'node': No such file or directory`.
|
# binary and then dies on `env: 'node': No such file or directory`.
|
||||||
candidates+=("$PANE_HOME/.mosaic/node/current/bin")
|
candidates+=("$PANE_HOME/.mosaic/node/current/bin")
|
||||||
|
|||||||
Reference in New Issue
Block a user