Dockerfile

FROM node:19-alpine AS base

LABEL MAINTAINER="Glib Garanin <glebgar567@gmail.com>"

ARG PNPM_VERSION=7.27.0
ARG BASE_API_URL
ENV BASE_API_URL=${BASE_API_URL}
ARG UTTERNANCES_REPOSITORY_NAME
ENV UTTERNANCES_REPOSITORY_NAME=${UTTERNANCES_REPOSITORY_NAME}
ARG SENTRY_DSN
ENV SENTRY_DSN=${SENTRY_DSN}
ARG VITE_SENTRY_AUTH_TOKEN
ENV VITE_SENTRY_AUTH_TOKEN=${VITE_SENTRY_AUTH_TOKEN}
ARG MONOBANK_JAR_URL
ENV MONOBANK_JAR_URL=${MONOBANK_JAR_URL}
# I'm making it enviroment variable so that Sentry can automatically
# determine a release name. Without this code on digital ocean it just crashes during build phase
ARG CF_PAGES_COMMIT_SHA
ENV CF_PAGES_COMMIT_SHA=${CF_PAGES_COMMIT_SHA}


RUN npm install -g pnpm@$PNPM_VERSION
WORKDIR /root/frontend-app

FROM base AS builder
COPY pnpm-lock.yaml .npmrc package.json pnpm-workspace.yaml ./
COPY app/package.json ./app/package.json
RUN --mount=type=cache,id=pnpm-store,target=/root/.pnpm-store\
 pnpm install --filter "app" --frozen-lockfile \
 --unsafe-perm\
 # ↑ Docker runs pnpm as root and then pnpm won't run package scripts unless we pass this arg
 | grep -v "cross-device link not permitted\|Falling back to copying packages from store"
 # ↑ This inverted grep match is because using Docker's 'cache' mount type
 # causes Docker to place the pnpm content-addressable store on a different virtual drive,
 # which prohibits pnpm from symlinking its content to its virtual store (in node_modules/.pnpm),
 # and that causes pnpm to fall back on copying the files. And that's fine,
 # except pnpm emits a lot of warnings doing that, so here we filter out those warnings.

COPY . .
RUN NODE_OPTIONS=--max_old_space_size=8192 NODE_ENV=production pnpm run app:build