create-nuxt-base 2.6.3 → 2.6.5

package/nuxt-base-template/scripts/check-server-start.sh

@@ -1,37 +1,67 @@
 #!/usr/bin/env bash
+# Verify the built Nuxt server boots and stays up, then exit cleanly.
+#
+# Previously this script also streamed logs via a parallel `tail -f` and waited
+# on both PIDs on EXIT. On macOS / bash that pattern hangs intermittently:
+# `tail -f` does not always honor SIGTERM while blocked on the kqueue file
+# watch, so `wait $TAIL_PID` blocks indefinitely and the surrounding
+# `pnpm run check` never returns. We now skip the live stream and print the
+# relevant log excerpt at the end instead.
+
 set -e
 
-# Temp file for server output
-LOG_FILE=$(mktemp)
+LOG_FILE=$(mktemp -t nuxt-check-server.XXXXXX)
 
-# Start the built Nuxt server in background, redirect output to log file
-# The build step already ran before this script is called
-node .output/server/index.mjs > "$LOG_FILE" 2>&1 &
-SERVER_PID=$!
+cleanup() {
+  if [[ -n "${SERVER_PID:-}" ]]; then
+    # SIGTERM first, then SIGKILL if still alive after ~2s. We do NOT `wait`
+    # on the child — it was the original hang. Nitro can take a moment to
+    # unwind its listeners; the escalation gives it that moment.
+    kill "$SERVER_PID" 2>/dev/null || true
+    for _ in 1 2 3 4; do
+      kill -0 "$SERVER_PID" 2>/dev/null || break
+      sleep 0.5
+    done
+    kill -9 "$SERVER_PID" 2>/dev/null || true
+  fi
+  rm -f "$LOG_FILE"
+}
+trap cleanup EXIT
 
-# Show log output in real-time
-tail -f "$LOG_FILE" &
-TAIL_PID=$!
+# Pick a free port so the check passes regardless of what is running on
+# 3000/3001 (sister API dev server, another nuxt instance, …). Strip
+# ANSI color escape sequences from the command output — when this
+# script runs under a workspace runner like lerna/nx, stdout may be
+# wrapped and color codes ("\x1b[33m...\x1b[39m") injected. Those would
+# land inside FREE_PORT and crash Nitro with
+# `ERR_SOCKET_BAD_PORT options.port ... Received type string ('<codes>50604<codes>')`.
+# A naïve `tr -cd '0-9'` makes it worse because the color codes contain
+# digits (33, 39) themselves; sed only on the escape pattern keeps the
+# port digits intact.
+# Use NITRO_PORT rather than PORT — Nitro 2.13.3 reads PORT as a string
+# without parseInt and feeds it straight into net.Server#listen.
+FREE_PORT=$(node -e "const s=require('net').createServer();s.listen(0,'127.0.0.1',()=>{const p=s.address().port;s.close(()=>console.log(p));});" | sed $'s/\x1b\\[[0-9;]*m//g' | tr -d '[:space:]')
+echo "Using free port: $FREE_PORT"
 
-# Ensure cleanup on exit: kill server, tail, and remove temp file
-trap 'kill $SERVER_PID $TAIL_PID 2>/dev/null; wait $SERVER_PID $TAIL_PID 2>/dev/null || true; rm -f "$LOG_FILE"' EXIT
+NITRO_PORT=$FREE_PORT node .output/server/index.mjs >"$LOG_FILE" 2>&1 &
+SERVER_PID=$!
+# Remove from job table so bash does not print "Terminated: 15" on SIGTERM
+disown "$SERVER_PID" 2>/dev/null || true
 
-# Wait for the Nitro server ready message (max 60 seconds)
-for i in $(seq 1 60); do
+for _ in $(seq 1 60); do
   if grep -q "Listening on\|Nitro ready\|Local:" "$LOG_FILE" 2>/dev/null; then
-    echo ""
+    tail -n 5 "$LOG_FILE"
     echo "Server started successfully - check complete"
     exit 0
   fi
-  # Check if server process died unexpectedly
-  if ! kill -0 $SERVER_PID 2>/dev/null; then
-    echo ""
-    echo "Server process exited unexpectedly"
+  if ! kill -0 "$SERVER_PID" 2>/dev/null; then
+    echo "Server process exited unexpectedly. Full log:"
+    cat "$LOG_FILE"
     exit 1
   fi
   sleep 1
 done
 
-echo ""
-echo "Server failed to start within 60 seconds"
+echo "Server failed to start within 60 seconds. Last 30 log lines:"
+tail -n 30 "$LOG_FILE"
 exit 1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-nuxt-base",
-  "version": "2.6.3",
+  "version": "2.6.5",
   "description": "Starter to generate a configured environment with VueJS, Nuxt, Tailwind, Linting, Unit Tests, Playwright etc.",
   "license": "MIT",
   "author": "lenne.Tech GmbH",