deploy
8 traces
- ✘ [ERROR] Unknown arguments: ..., publish — wrangler publish was removed in Wrangler v4; use wrangler deployA CI job or README command that worked for years fails after Wrangler resolves to v4 (e.g. Fix: Pin wrangler as a devDependency (npm i -D wrangler@4) rather than installing it globally in CI, so the version is explicit.
- macOS openrsync 'unexpected end of file' when rsync -az to a Linux serverOn recent macOS, /usr/bin/rsync is openrsync, not GNU rsync. Fix: Either avoid the options that trip it: or skip rsync entirely and stream a tarball over ssh: COPYFILEDISABLE=1 keeps macOS from adding AppleDouble .
- rsync/tar --exclude data silently drops code directories named data (e.g. Next.js app/data route) — anchor the patternAfter deploying with rsync --exclude data (meant to protect the server's runtime data/ directory), a page at /data (source in app/data/) returns 404 in production for weeks while working locally. Fix: Anchor excludes…
- OOM killer kills a live next-server during npm run build on the same production VM (Turbopack build spike)On a 4-core/8 GB VM hosting many pm2-managed Next.js apps, a customer app randomly dies and restarts. Fix: Do not build on the serving box.
- SQLite app shows 0 rows after deploying a DB file: `next build` opened the DB and left a stale -wal/-shm beside itA Next.js app backed by better-sqlite3 was built on the server, and then a known-good database (verified with pragma integritycheck and row counts) was copied into its data directory. Fix: 1.
- tar: Ignoring unknown extended header keyword 'LIBARCHIVE.xattr.com.apple.provenance' aborts a set -e deploy halfwayA deploy piped a macOS-made tarball to a Linux server: tar czf - .next app lib | ssh server 'set -e; ...; tar xzf - -C .next.new; mv ...'. Fix: Create the archive without macOS metadata and strip AppleDouble files:…
- tar from macOS ships ._* AppleDouble files that break Linux deploy scripts — use COPYFILE_DISABLE=1A deploy script built a Next.js app on a Mac, ran tar czf build.tgz .next app lib, extracted it on Linux, then swapped directories under set -e. Fix: Clean up an already-polluted tree with find .
- Failed to load external module sharp-<hash>: ERR_MODULE_NOT_FOUND after shipping a Turbopack .next build to a serverA Next.js 16 app built with Turbopack on one machine (macOS) and shipped as a .next tarball to a Linux server starts fine (✓ Ready), but every route that uses sharp (image thumbnails, PDF stamping) returns 500. Fix:…