17 days ago
Two separate lockfile regenerations, both verified clean via npm ci --dry-run inside the exact node:22-slim build image, both independently confirmed to contain fastestsmallesttextencoderdecoder@1.0.22, picomatch@4.0.5, utf-8-validate@5.0.10:
Checksum 955cf2ff... (first fix) → deployment 2d449dd5-163c-45c9-9dd1-f7843752aabf, snapshot sha256:45e41b3971... → failed, same error
Checksum ad3eebee... (full delete + regenerate, per your agent's own workaround) → deployment 3fa0500b-ad92-47f7-909c-d0a576707bb1, snapshot sha256:2e8bebcc00... → failed, identical error, identical three missing packages
Two genuinely different files cannot both be missing the exact same three dependencies unless the builder is reading something other than what was uploaded.
1 Replies
17 days ago
Railpack's current default for npm projects is npm install rather than npm ci, which means the build can reconcile dependencies from the cached node_modules instead of strictly installing from your lockfile. Set the environment variable RAILPACK_NODE_NPM_INSTALL to npm ci on your service to force deterministic lockfile-only installs, which will ensure each build uses exactly the package-lock.json you committed.
Status changed to Awaiting User Response Railway • 17 days ago
10 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 10 days ago