gui.do
Barazo default frontend
barazo.forum
fix(docker): use transpilePackages for plugin frontend, skip tsc build (#204)
Plugin exports now point to source .ts/.tsx files. Next.js compiles
them via transpilePackages, eliminating the need for a separate tsc
build that fails without @types/react in Docker. CI simplified too —
just clone the repo, no build needed.
authored by
Guido X Jansen
and committed by
GitHub
9bf0b29d
2a378702
+4
-7
+2
-5
.github/actions/setup/action.yml
+2
-5
.github/actions/setup/action.yml
···
25
25
git clone --depth 1 https://github.com/singi-labs/barazo-lexicons.git ../barazo-lexicons
26
26
cd ../barazo-lexicons && pnpm install --ignore-scripts && pnpm run build
27
27
28
-
- name: Clone and build barazo-plugins (frontend only)
28
+
- name: Clone barazo-plugins
29
29
shell: bash
30
-
run: |
31
-
git clone --depth 1 https://github.com/singi-labs/barazo-plugins.git ../barazo-plugins
32
-
cd ../barazo-plugins && pnpm install --ignore-scripts
33
-
cd packages/plugin-signatures && npx tsc -p tsconfig.frontend.json
30
+
run: git clone --depth 1 https://github.com/singi-labs/barazo-plugins.git ../barazo-plugins
34
31
35
32
- name: Install dependencies
36
33
shell: bash
+2
-2
Dockerfile
+2
-2
Dockerfile
···
43
43
# Copy web source
44
44
COPY barazo-web/ ./barazo-web/
45
45
46
-
# Build lexicons and plugin frontend first (workspace dependencies), then Next.js
46
+
# Build lexicons first (workspace dependency), then Next.js.
47
+
# Plugin frontend source is compiled by Next.js via transpilePackages.
47
48
ENV NEXT_TELEMETRY_DISABLED=1
48
49
RUN pnpm --filter @singi-labs/lexicons build && \
49
-
cd barazo-plugins/packages/plugin-signatures && npx tsc -p tsconfig.frontend.json --skipLibCheck && cd /workspace && \
50
50
pnpm --filter @singi-labs/web build
51
51
52
52
# ---------------------------------------------------------------------------