Barazo default frontend
barazo.forum
fix(docker): include barazo-plugins in build context (#202)
The web Dockerfile didn't copy the plugins workspace package, so
Turbopack couldn't resolve @barazo/plugin-signatures during next build.
Adds the plugin package.json to the deps stage and copies source +
builds frontend types in the builder stage.
authored by
Guido X Jansen
and committed by
GitHub
7c1e7b69
4e496387
+6
-1
+6
-1
Dockerfile
+6
-1
Dockerfile
···
18
18
COPY barazo-lexicons/package.json ./barazo-lexicons/
19
19
COPY barazo-api/package.json ./barazo-api/
20
20
COPY barazo-web/package.json ./barazo-web/
21
+
COPY barazo-plugins/packages/plugin-signatures/package.json ./barazo-plugins/packages/plugin-signatures/
21
22
22
23
# Install all dependencies
23
24
RUN pnpm install --frozen-lockfile
···
36
37
# Copy lexicons source (workspace dependency)
37
38
COPY barazo-lexicons/ ./barazo-lexicons/
38
39
40
+
# Copy plugins source (workspace dependency — frontend components bundled by Next.js)
41
+
COPY barazo-plugins/ ./barazo-plugins/
42
+
39
43
# Copy web source
40
44
COPY barazo-web/ ./barazo-web/
41
45
42
-
# Build lexicons first (workspace dependency), then Next.js
46
+
# Build lexicons and plugin frontend first (workspace dependencies), then Next.js
43
47
ENV NEXT_TELEMETRY_DISABLED=1
44
48
RUN pnpm --filter @singi-labs/lexicons build && \
49
+
cd barazo-plugins/packages/plugin-signatures && npx tsc -p tsconfig.frontend.json && cd /workspace && \
45
50
pnpm --filter @singi-labs/web build
46
51
47
52
# ---------------------------------------------------------------------------