cm_whatsapp_bot_v1/docker/web.Dockerfile
yiekheng 7d3d34af7f fix(docker): copy workspace packages' node_modules into web runtime
Web container booted but every page logged:
  Error: Cannot find module 'rrule'
  at /app/packages/shared/dist/rrule.js

Next's standalone tracer copied packages/shared/dist/*.js into the
standalone output but didn't follow their require("rrule") chain
into packages/shared/node_modules — pnpm's symlinked dep layout
isn't always followable by the tracer. Same risk for any other
shared/db transitive dep (luxon, cron-parser, drizzle-orm, pg,
bcryptjs).

Copy packages/shared/node_modules and packages/db/node_modules into
the runtime stage explicitly so the standalone require chain
resolves. Bot Dockerfile already ships full node_modules so it's
unaffected.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-10 22:31:14 +08:00

59 lines
2.6 KiB
Docker

FROM node:22-alpine AS base
RUN npm install -g pnpm@9.12.0
WORKDIR /app
FROM base AS deps
COPY package.json pnpm-workspace.yaml pnpm-lock.yaml ./
COPY apps/web/package.json apps/web/
COPY packages/db/package.json packages/db/
COPY packages/shared/package.json packages/shared/
RUN pnpm install --frozen-lockfile
FROM base AS build
COPY --from=deps /app/node_modules /app/node_modules
COPY --from=deps /app/apps/web/node_modules /app/apps/web/node_modules
COPY --from=deps /app/packages/db/node_modules /app/packages/db/node_modules
COPY --from=deps /app/packages/shared/node_modules /app/packages/shared/node_modules
COPY tsconfig.base.json turbo.json ./
COPY apps/web apps/web
COPY packages/db packages/db
COPY packages/shared packages/shared
# Placeholder env values during `next build`'s "Collecting page data"
# pass. Next bundles `lib/db.ts` (`createClient(env.DATABASE_URL)`) and
# `actions/auth.ts` (uses AUTH_SECRET) into route bundles; their
# top-level env access fires when Next imports the route to inspect
# its config (the route's own `export const dynamic = "force-dynamic"`
# stops handler execution, NOT module evaluation).
#
# pg.Pool is lazy — it stores the URL and only connects on the first
# query — so a build-time placeholder never opens a socket. The
# placeholders are scoped to this RUN layer (each Dockerfile RUN is
# its own shell); nothing leaks into the runtime image.
RUN export DATABASE_URL=postgres://build:build@localhost:5432/build && \
export AUTH_SECRET=build-time-placeholder-not-used-at-runtime && \
pnpm --filter @cmbot/shared build && \
pnpm --filter @cmbot/db build && \
pnpm --filter @cmbot/web build
FROM base AS runtime
ENV NODE_ENV=production
ENV PORT=3000
ENV HOSTNAME=0.0.0.0
COPY --from=build /app/apps/web/.next/standalone ./
COPY --from=build /app/apps/web/.next/static ./apps/web/.next/static
COPY --from=build /app/apps/web/public ./apps/web/public
# Next's standalone tracer copied packages/shared/dist/*.js but
# missed their transitive deps — packages/shared/dist/rrule.js does
# require("rrule") and the rrule node_modules entry never landed in
# the standalone output (pnpm's symlinked layout often confuses the
# tracer). Copy the workspace packages' node_modules trees in
# directly so the require chain resolves at runtime.
COPY --from=build /app/packages/shared/node_modules ./packages/shared/node_modules
COPY --from=build /app/packages/db/node_modules ./packages/db/node_modules
# Reuse the `node` user (UID/GID 1000) that node:alpine ships with —
# `addgroup -g 1000 app` collided with the pre-existing node group.
RUN chown -R node:node /app
USER node
EXPOSE 3000
CMD ["node", "apps/web/server.js"]