lfg2025/archy
1
0
Fork 0
Code Issues 27 Pull Requests 5 Actions Packages Projects Releases 7 Wiki Activity

fix(release): surface frontend build failures instead of hiding them

Browse Source 
`npm run build 2>&1 | tail -3` threw away npm's exit status, so a failed
build was indistinguishable from a good one. The run continued and blamed
the next check instead — "the frontend build no-opped or its output is
stale" — which points at a stale dist rather than at the build error that
actually happened, and cost a diagnosis cycle today.

Success still prints the same quiet 3 lines; a failure now prints the real
error, keeps the full log, and aborts on the spot.

Verified both branches with a stubbed npm.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
archipelago
2026-08-20 05:24:37 -04:00
co-authored by Claude Opus 5
parent 3d7de3e902
commit e03a2fed89
1 changed files with 12 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
scripts/create-release.sh
+12 -1
View File
@@ -155,7 +155,18 @@ cd "$PROJECT_ROOT"
echo "[4/8] Building frontend..." echo "[4/8] Building frontend..."
cd "$PROJECT_ROOT/neode-ui" cd "$PROJECT_ROOT/neode-ui"
npm run build 2>&1 | tail -3 # `| tail -3` discards npm's exit status, so a FAILED build looked identical
# to a successful one and the run marched on to report the far more
# confusing "build no-opped or its output is stale" a few lines later.
# Keep the quiet 3-line output, but surface the real error when it breaks.
build_log=$(mktemp -t neode-build.XXXXXX.log)
if npm run build >"$build_log" 2>&1; then
tail -3 "$build_log"; rm -f "$build_log"
else
echo "Error: the frontend build FAILED — full log kept at $build_log" >&2
tail -40 "$build_log" >&2
exit 1
fi
cd "$PROJECT_ROOT" cd "$PROJECT_ROOT"
# npm run build wipes web/dist — fold AIUI straight back in. The OTA tarball # npm run build wipes web/dist — fold AIUI straight back in. The OTA tarball