fix: Dockerfile uses npm prune instead of npm ci for production deps

Browse Source

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.

...

This commit is contained in:

Santhosh Janardhanan

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

parent 792fafc661

commit ca583ea6c9

2 changed files with 5 additions and 4 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

BIN

.env.docker

Binary file not shown.