mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 02:54:26 +00:00
kevinveenbirkenbachandClaude Opus 5
ce244132a6
test-unit-javascript ran `node --test` without declaring where node comes from, while its python sibling declares `install`. On a bare distro image the target died with `exec: node: not found` (127), which took down the pre-commit hook and all five test-workspace jobs. The installer stack already knows how to pull a command from the system package manager; node was simply missing from the table. Wiring the target to install-node provisions it the same way php, ruby and npm are provisioned, and fails loudly when the runtime cannot be installed rather than skipping the suite. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
8 lines
235 B
Bash
Executable File
8 lines
235 B
Bash
Executable File
#!/usr/bin/env bash
|
|
# shellcheck shell=bash
|
|
set -euo pipefail
|
|
SCRIPT_DIR="$(cd -- "$(dirname -- "${BASH_SOURCE[0]}")" && pwd)"
|
|
REPO_ROOT="$(cd -- "${SCRIPT_DIR}/../.." && pwd)"
|
|
cd "${REPO_ROOT}"
|
|
exec python3 -m utils.install.node "$@"
|