Lucas RayanandClaude Opus 5 64c9efe078 #21: keep devDependencies in the build stage regardless of NODE_ENV ...

The deployment sets NODE_ENV=production, and npm omits devDependencies
when it is set - so "npm ci" in the build stage installed no typescript
and "npm run build" failed with exit 127, command not found. The first
Coolify deployment died there.

The build stage now asks for them explicitly rather than depending on the
environment it happens to run in. Reproduced by building all three images
with NODE_ENV=production before and after.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

2026-08-02 14:08:09 -03:00

..

src

#1: implement F0 foundation - monorepo, migrations, Go domain layer, service skeletons, CI

2026-07-23 05:05:46 -03:00

Dockerfile

#21: keep devDependencies in the build stage regardless of NODE_ENV

2026-08-02 14:08:09 -03:00

package-lock.json

#1: implement F0 foundation - monorepo, migrations, Go domain layer, service skeletons, CI

2026-07-23 05:05:46 -03:00

package.json

#21: make the stack deployable, and document how

2026-08-02 13:33:51 -03:00

tsconfig.build.json

#21: make the stack deployable, and document how

2026-08-02 13:33:51 -03:00

tsconfig.json

#1: implement F0 foundation - monorepo, migrations, Go domain layer, service skeletons, CI

2026-07-23 05:05:46 -03:00

vitest.config.ts

#1: implement F0 foundation - monorepo, migrations, Go domain layer, service skeletons, CI

2026-07-23 05:05:46 -03:00