netcracker/ai-for-dummies
3
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix: gate the launcher's npm ci on a lockfile, not package.json

Browse Source 
The pre-existing root package.json has two scripts and no dependencies, and
there is no package-lock.json until task 01 scaffolds Astro, so every launch
died on `npm ci` before reaching the agent.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Marcos Paulo
2026-09-05 01:22:00 +00:00
parent 1cc9469d2d
commit 88eecb1c71
1 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.agents/scripts/launch.sh
+4 -3
View File
@@ -56,9 +56,10 @@ else
git worktree add "$dir" -b "$branch" "$base" git worktree add "$dir" -b "$branch" "$base"
fi fi
# npm ci only once task 01 has produced a package.json. Before that there is no # npm ci only once task 01 has produced a lockfile. The pre-existing root
# toolchain to install, and no hooks to verify. # package.json carries two scripts and no dependencies, so before task 01 there
if [ -f "$dir/package.json" ]; then # is no toolchain to install and no hooks to verify.
if [ -f "$dir/package-lock.json" ]; then
( cd "$dir" && npm ci --prefer-offline && .agents/scripts/verify-hooks.sh ) ( cd "$dir" && npm ci --prefer-offline && .agents/scripts/verify-hooks.sh )
fi fi