Santhosh Janardhanan ca583ea6c9 fix: Dockerfile uses npm prune instead of npm ci for production deps ...

The run stage no longer runs npm ci --omit=dev (which fails when
package-lock.json and the Docker environment's resolved deps are
out of sync, e.g. @emnapi/* transitive deps from adapter-node).

Instead, the build stage runs npm prune --omit=dev after building,
and the run stage copies the already-pruned node_modules. This
avoids any lock file sync issues across different environments.

2026-04-13 00:36:12 -04:00

62 B

Raw Blame History

View Raw