Skip to content

chore(package): migrate to pnpm workspace and update Docker contexts #520

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
l1ttps wants to merge 2 commits into from
Closed

chore(package): migrate to pnpm workspace and update Docker contexts #520

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
080abed
chore(package): migrate to pnpm workspace and update Docker contexts
l1ttps Jul 7, 2026
d7976cb
fix(ci): resolve pnpm version conflict and corepack not found in Docker
l1ttps Jul 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
48 changes: 45 additions & 3 deletions .dockerignore
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,46 @@
node_modules
bun.lockb
npm-debug.log
**/node_modules/
**/dist/
**/.git/
.gitignore
.gitattributes
*.md
*.log
npm-debug.log*
pnpm-debug.log*
yarn-debug.log*
yarn-error.log*
lerna-debug.log*
.env
.env.*
!.env.example
.github/
.husky/
.vscode/
.idea/
.worktrees/
worktrees/
.open-api/
.agent/
.agents/
.windsurf/
.claude/
.qwen/
.omo/
.temp/
.tmp/
.coverage/
coverage/
*.storage/
worker/oasm-tools/
worker/dist/
worker/agent-sessions/
console/coverage/
console/e2e/playwright-report/
console/e2e/test-results/
console/e2e/.auth/
console/sw.js
grpc-client/
docs/
Dockerfile
.dockerignore
bun.lockb
2 changes: 1 addition & 1 deletion .github/workflows/build-nightly.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -84,7 +84,7 @@ jobs:
--cache-to=type=registry,ref=${{ env.IMAGE_NAME }}-${{ matrix.service }}:buildcache,mode=max \
--tag ${{ env.IMAGE_NAME }}-${{ matrix.service }}:dev \
--file ./${{ matrix.service == 'api' && 'core-api' || matrix.service }}/Dockerfile \
./${{ matrix.service == 'api' && 'core-api' || matrix.service }}
${{ matrix.service == 'worker' && './worker' || '.' }}

- name: Run Trivy vulnerability scanner
uses: aquasecurity/trivy-action@master
Expand Down
2 changes: 1 addition & 1 deletion .github/workflows/build-release.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -117,4 +117,4 @@ jobs:
--tag ${{ env.IMAGE_NAME }}-${{ matrix.service }}:latest \
--tag ${{ env.IMAGE_NAME }}-${{ matrix.service }}:${{ github.ref_name }} \
--file ./${{ matrix.service == 'api' && 'core-api' || matrix.service }}/Dockerfile \
./${{ matrix.service == 'api' && 'core-api' || matrix.service }}
${{ matrix.service == 'worker' && './worker' || '.' }}
6 changes: 4 additions & 2 deletions .github/workflows/check-build.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,8 @@ jobs:
- name: Build Docker image (Console)
uses: docker/build-push-action@v5
with:
context: ./console
context: .
file: ./console/Dockerfile
push: false
load: true
tags: oasm/oasm-console:test
Expand All @@ -78,7 +79,8 @@ jobs:
- name: Build Docker image (Core API)
uses: docker/build-push-action@v5
with:
context: ./core-api
context: .
file: ./core-api/Dockerfile
push: false
load: true
tags: oasm/oasm-api:test
Expand Down
18 changes: 12 additions & 6 deletions .github/workflows/check-lint.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,15 +7,19 @@ on:
paths:
- 'core-api/**'
- 'console/**'
- 'package*.json'
- 'pnpm-lock.yaml'
- 'pnpm-workspace.yaml'
- 'package.json'
- 'tsconfig*.json'
pull_request:
branches:
- '**'
paths:
- 'core-api/**'
- 'console/**'
- 'package*.json'
- 'pnpm-lock.yaml'
- 'pnpm-workspace.yaml'
- 'package.json'
- 'tsconfig*.json'

jobs:
Expand All @@ -29,15 +33,17 @@ jobs:
- name: Checkout code
uses: actions/checkout@v5

- name: Install pnpm
uses: pnpm/action-setup@v6

- name: Setup Node.js
uses: actions/setup-node@v6
with:
node-version: '22'
cache: 'npm'
cache-dependency-path: package-lock.json
cache: 'pnpm'

- name: Install dependencies
run: npm ci --ignore-scripts
run: pnpm install --frozen-lockfile

- name: Run lint
run: npm run lint --workspace=${{ matrix.service }}
run: pnpm run lint --filter=${{ matrix.service }}
Comment on lines +36 to +49

@coderabbitai coderabbitai Bot Jul 7, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf '\n== workflow ==\n'
sed -n '1,120p' .github/workflows/check-lint.yml

printf '\n== package manifests ==\n'
for f in core-api/package.json console/package.json; do
  if [ -f "$f" ]; then
    echo "-- $f"
    sed -n '1,80p' "$f"
  else
    echo "-- missing: $f"
  fi
done

Repository: oasm-platform/open-asm

Length of output: 6823

🏁 Script executed:

#!/bin/bash
set -euo pipefail

if command -v pnpm >/dev/null 2>&1; then
  printf '\n== pnpm version ==\n'
  pnpm --version

  printf '\n== pnpm run help excerpt ==\n'
  pnpm run --help | sed -n '1,220p'
else
  echo "pnpm not installed in this environment"
fi

Repository: oasm-platform/open-asm

Length of output: 10220

🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf '\n== root package.json ==\n'
if [ -f package.json ]; then
  sed -n '1,120p' package.json
else
  echo "missing package.json"
fi

printf '\n== pnpm docs excerpt (local help) ==\n'
pnpm help run | sed -n '1,180p'

Repository: oasm-platform/open-asm

Length of output: 11014

🌐 Web query:

pnpm run options listed after the script's name are passed to the executed script --filter after script name

💡 Result:

In pnpm, options listed after a script's name are passed directly to the executed script, while options for the pnpm run command itself must be placed before the script's name [1][2]. Regarding your specific question about the --filter flag: the --filter option is a command-level option used to restrict which packages a command runs on [3][4]. Because it is a pnpm command-level option, it must be placed before the script name to be parsed by pnpm [4]. If you place --filter after the script name (e.g., pnpm run <script> --filter ), pnpm will not interpret it as a filtering instruction for the command [5]. Instead, it will pass the --filter argument directly to the script you are executing, which may cause the script to fail if it does not recognize that argument [1][2][5]. To correctly use filtering with a script, structure your command as follows: pnpm --filter <package_selector> run <script_name> This ensures the filter is applied to the pnpm command, and any additional arguments intended for your script can then be appended after the script name [2].

Citations:

Move --filter before run
pnpm run lint --filter=${{ matrix.service }} forwards --filter to the lint script instead of scoping pnpm, so this step resolves to the root package and fails because the root package.json has no lint script. Use pnpm --filter=${{ matrix.service }} run lint instead.

Proposed fix 
-        run: pnpm run lint --filter=${{ matrix.service }}
+        run: pnpm --filter=${{ matrix.service }} run lint
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- name: Install pnpm
uses: pnpm/action-setup@v6
with:
version: 11
- name: Setup Node.js
uses: actions/setup-node@v6
with:
node-version: '22'
cache: 'npm'
cache-dependency-path: package-lock.json
cache: 'pnpm'
- name: Install dependencies
run: npm ci --ignore-scripts
run: pnpm install --frozen-lockfile
- name: Run lint
run: npm run lint --workspace=${{ matrix.service }}
run: pnpm run lint --filter=${{ matrix.service }}
- name: Install pnpm
uses: pnpm/action-setup@v6
with:
version: 11
- name: Setup Node.js
uses: actions/setup-node@v6
with:
node-version: '22'
cache: 'pnpm'
- name: Install dependencies
run: pnpm install --frozen-lockfile
- name: Run lint
run: pnpm --filter=${{ matrix.service }} run lint
🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/check-lint.yml around lines 36 - 51, The lint workflow
step is passing --filter to the lint script instead of to pnpm, so the command
runs at the root package and misses the service-specific script. Update the run
command in the workflow to scope pnpm first, using the same matrix.service value
with pnpm --filter before run lint, so the existing lint script is executed in
the intended package.

22 changes: 12 additions & 10 deletions .github/workflows/check-test.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,37 +6,39 @@ on:
- '**'
paths:
- 'core-api/**'
- 'package*.json'
- 'pnpm-lock.yaml'
- 'pnpm-workspace.yaml'
- 'package.json'
- 'tsconfig*.json'
pull_request:
branches:
- '**'
paths:
- 'core-api/**'
- 'package*.json'
- 'pnpm-lock.yaml'
- 'pnpm-workspace.yaml'
- 'package.json'
- 'tsconfig*.json'

jobs:
test:
name: Check Test
runs-on: ubuntu-latest
defaults:
run:
working-directory: core-api
steps:
- name: Checkout code
uses: actions/checkout@v5
Comment on lines 28 to 29

@coderabbitai coderabbitai Bot Jul 7, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔒 Security & Privacy | 🟡 Minor | ⚡ Quick win

Checkout doesn't disable credential persistence.

zizmor flags this checkout for artifact credential persistence (artipacked): persist-credentials: false isn't set, so the GITHUB_TOKEN remains in the local git config for the rest of the job.

🛡️ Proposed fix 
       - name: Checkout code
         uses: actions/checkout@v5
+        with:
+          persist-credentials: false
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
- name: Checkout code
uses: actions/checkout@v5
- name: Checkout code
uses: actions/checkout@v5
with:
persist-credentials: false
🧰 Tools
🪛 zizmor (1.26.1)

[warning] 28-29: credential persistence through GitHub Actions artifacts (artipacked): does not set persist-credentials: false

(artipacked)

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/check-test.yml around lines 28 - 29, The Checkout code
step in the workflow leaves git credentials persisted, which can expose the
GITHUB_TOKEN later in the job. Update the actions/checkout usage in the
check-test workflow to explicitly disable credential persistence by setting
persist-credentials to false on the Checkout code step so the repository config
does not retain the token after checkout.

Source: Linters/SAST tools


- name: Install pnpm
uses: pnpm/action-setup@v6

- name: Setup Node.js
uses: actions/setup-node@v6
with:
node-version: '22'
cache: 'npm'
cache: 'pnpm'

- name: Install dependencies
run: npm ci --ignore-scripts
working-directory: core-api
run: pnpm install --frozen-lockfile

- name: Run tests
run: npm run test
working-directory: core-api
run: pnpm run test --filter core-api
Comment on lines 23 to +44

@coderabbitai coderabbitai Bot Jul 7, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf '\n== Files ==\n'
git ls-files .github/workflows/check-test.yml .github/workflows/check-lint.yml || true

printf '\n== check-test.yml ==\n'
sed -n '1,220p' .github/workflows/check-test.yml

printf '\n== check-lint.yml ==\n'
sed -n '1,220p' .github/workflows/check-lint.yml

printf '\n== Search for working-directory and filter usage ==\n'
rg -n "defaults\.run\.working-directory|--filter|pnpm run test|pnpm --filter" .github/workflows

Repository: oasm-platform/open-asm

Length of output: 2589

🌐 Web query:

pnpm run options listed after the script's name are passed to the executed script --filter before run documentation

💡 Result:

In pnpm, command-line arguments and options placed after the script name are passed directly to the executed script [1][2]. Any options intended for the pnpm CLI itself must be placed before the script name [1][2]. Regarding the --filter option: 1. Placement: The --filter option is a pnpm CLI option used to restrict commands to specific subsets of packages in a workspace [3][4]. Because it is an option for the pnpm CLI, it must be placed before the script's name (or before the run command itself) to be correctly parsed and executed [5][2]. 2. Syntax: The correct structure for using a filter with a run command is: pnpm --filter <package_selector> run <script_name> [args_for_script] Placing --filter after the script name would result in it being passed as an argument to the script itself, rather than being interpreted by pnpm as a workspace filtering command [1][2].

Citations:

🏁 Script executed:

#!/bin/bash
set -euo pipefail

python3 - <<'PY'
from pathlib import Path

for path in [Path('.github/workflows/check-test.yml'), Path('.github/workflows/check-lint.yml')]:
    print(f'## {path}')
    if path.exists():
        for i, line in enumerate(path.read_text().splitlines(), 1):
            if 'defaults.run.working-directory' in line or '--filter' in line or 'pnpm run test' in line or 'pnpm --filter' in line:
                print(f'{i}: {line}')
    else:
        print('missing')
PY

Repository: oasm-platform/open-asm

Length of output: 343

🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf '\n== root package.json ==\n'
sed -n '1,220p' package.json

printf '\n== core-api package.json ==\n'
sed -n '1,220p' core-api/package.json

printf '\n== workspace package list ==\n'
find . -maxdepth 2 -name package.json -not -path './node_modules/*' | sort

Repository: oasm-platform/open-asm

Length of output: 5370

Use pnpm’s filter before run

pnpm run test --filter core-api doesn’t scope the workspace; --filter is forwarded as a script arg, so pnpm still looks for test in the root package. Since the root has no test script, this step fails instead of running core-api tests.

Proposed fix 
-        run: pnpm run test --filter core-api
+        run: pnpm --filter core-api run test
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
jobs:
test:
name: Check Test
runs-on: ubuntu-latest
defaults:
run:
working-directory: core-api
steps:
- name: Checkout code
uses: actions/checkout@v5
- name: Install pnpm
uses: pnpm/action-setup@v6
with:
version: 11
- name: Setup Node.js
uses: actions/setup-node@v6
with:
node-version: '22'
cache: 'npm'
cache: 'pnpm'
- name: Install dependencies
run: npm ci --ignore-scripts
working-directory: core-api
run: pnpm install --frozen-lockfile
- name: Run tests
run: npm run test
working-directory: core-api
run: pnpm run test --filter core-api
jobs:
test:
name: Check Test
runs-on: ubuntu-latest
steps:
- name: Checkout code
uses: actions/checkout@v5
- name: Install pnpm
uses: pnpm/action-setup@v6
with:
version: 11
- name: Setup Node.js
uses: actions/setup-node@v6
with:
node-version: '22'
cache: 'pnpm'
- name: Install dependencies
run: pnpm install --frozen-lockfile
- name: Run tests
run: pnpm --filter core-api run test
🧰 Tools
🪛 zizmor (1.26.1)

[warning] 28-29: credential persistence through GitHub Actions artifacts (artipacked): does not set persist-credentials: false

(artipacked)

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/check-test.yml around lines 23 - 46, The test step is
passing --filter as an argument to the test script instead of scoping pnpm to
the core-api workspace, so it still resolves the root package’s test script.
Update the Run tests step in the check-test workflow to apply pnpm’s filter
before the run command, using the existing core-api filter target so the
workspace test script is executed correctly.

17 changes: 10 additions & 7 deletions .github/workflows/frontend-tests.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,10 +3,10 @@ name: Frontend Tests
on:
push:
branches: [main]
paths: ['console/**']
paths: ['console/**', 'pnpm-lock.yaml', 'pnpm-workspace.yaml']
pull_request:
branches: [main]
paths: ['console/**']
paths: ['console/**', 'pnpm-lock.yaml', 'pnpm-workspace.yaml']

permissions:
contents: read
Expand All @@ -17,15 +17,18 @@ jobs:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v5

- name: Install pnpm
uses: pnpm/action-setup@v6

- uses: actions/setup-node@v6
with:
node-version: '22'
cache: 'npm'
cache-dependency-path: package-lock.json
cache: 'pnpm'

- run: npm ci
- run: npm run test:run --workspace=console
- run: npm run test:coverage --workspace=console
- run: pnpm install --frozen-lockfile
- run: pnpm run test:run --filter console
- run: pnpm run test:coverage --filter console
Comment on lines +20 to +31

@coderabbitai coderabbitai Bot Jul 7, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Functional Correctness | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf 'Workflow excerpt:\n'
sed -n '1,120p' .github/workflows/frontend-tests.yml

printf '\nRelevant package scripts:\n'
git ls-files '**/package.json' | while read -r f; do
  if rg -n '"test:run"|"test:coverage"' "$f" >/dev/null; then
    printf '\n--- %s ---\n' "$f"
    rg -n '"test:run"|"test:coverage"|"name"' "$f"
  fi
done

printf '\nSearch for pnpm filter usage in workflows:\n'
rg -n "pnpm .*--filter|--filter .*pnpm|pnpm run .*--filter" .github . -g '!**/node_modules/**'

Repository: oasm-platform/open-asm

Length of output: 1690

🏁 Script executed:

#!/bin/bash
set -euo pipefail

node - <<'JS'
const {spawnSync} = require('child_process');
function run(args){
  const r = spawnSync('pnpm', args, {encoding:'utf8'});
  console.log(`$ pnpm ${args.join(' ')}`);
  console.log('exit', r.status);
  if (r.stdout) console.log('stdout:\n' + r.stdout.trim());
  if (r.stderr) console.log('stderr:\n' + r.stderr.trim());
  console.log('---');
}
run(['--version']);
JS

Repository: oasm-platform/open-asm

Length of output: 203

🏁 Script executed:

#!/bin/bash
set -euo pipefail

printf 'Workspace config:\n'
sed -n '1,120p' pnpm-workspace.yaml

printf '\nRoot package scripts:\n'
if [ -f package.json ]; then
  rg -n '"test:run"|"test:coverage"|"scripts"' package.json
  sed -n '1,140p' package.json
fi

printf '\npnpm run help excerpts:\n'
pnpm help run | sed -n '1,220p'

Repository: oasm-platform/open-asm

Length of output: 11361

🌐 Web query:

pnpm run --filter after script name forwarded to script pnpm CLI documentation

💡 Result:

In pnpm, any options or arguments provided after the script name are passed directly to the executed script, not to the pnpm CLI [1][2]. If you intend to use pnpm-specific flags—such as --filter, --parallel, or --stream—you must place them before the script name or before the run command itself [1][3][2][4]. For example, if you want to run a script named build with a filter, the command should be structured as follows: pnpm --filter <package_selector> run build Alternatively, you can place the pnpm flags before the run subcommand: pnpm run --filter <package_selector> build If you place these flags after the script name (e.g., pnpm run build --filter <package_selector>), pnpm will attempt to pass those arguments to the build script itself rather than using them to configure the pnpm execution [3][4]. This behavior was standardized in pnpm v7 to ensure that all arguments following the script name are treated as part of the script's own arguments [3][5][4].

Citations:

Move --filter before run

pnpm run test:run --filter console and pnpm run test:coverage --filter console pass --filter to vitest, so pnpm still looks for those scripts in the root package.json and the job fails. Use pnpm --filter console run test:run and pnpm --filter console run test:coverage instead.

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/frontend-tests.yml around lines 20 - 33, The frontend test
workflow is passing `--filter` to the script instead of pnpm, so the `test:run`
and `test:coverage` commands are resolved from the root package instead of the
`console` package. Update the workflow commands in the frontend tests job to use
pnpm’s filter flag before `run`, and keep the same `test:run` and
`test:coverage` script names so they execute in the `console` workspace.


- name: Upload coverage
uses: actions/upload-artifact@v4
Expand Down
1 change: 1 addition & 0 deletions .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -80,6 +80,7 @@ core-api/public/tools/*
worker/.configs.json
worker/agent-sessions/*
console/sw.js
console/workbox-*.js
.omo

# Test coverage
Expand Down
3 changes: 3 additions & 0 deletions .npmrc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
# pnpm configuration for Open-ASM monorepo
strict-peer-dependencies=false
resolution-mode=highest
32 changes: 20 additions & 12 deletions console/Dockerfile
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,30 +1,38 @@
FROM node:26-alpine AS base
# Install BASH to make our lives easier for entrypoint.sh...
RUN apk add --no-cache curl bash && \
npm install -g serve && \
npm install -g bun
npm install -g serve
ENV PNPM_HOME="/pnpm"
ENV PATH="$PNPM_HOME/bin:$PATH"
RUN npm install -g corepack && corepack enable

WORKDIR /app

FROM base AS builder

COPY package.json ./
WORKDIR /app

# Copy root workspace config and console package.json
COPY pnpm-lock.yaml pnpm-workspace.yaml package.json .npmrc ./
COPY console/package.json ./console/package.json

ENV NODE_ENV production
# Install all dependencies
RUN --mount=type=cache,id=pnpm,target=/pnpm/store pnpm install --frozen-lockfile
Comment on lines +15 to +20

@coderabbitai coderabbitai Bot Jul 7, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Functional Correctness | 🟠 Major | 🏗️ Heavy lift

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Inspect the actual workspace membership and .npmrc settings
cat pnpm-workspace.yaml
echo "---"
cat .npmrc
echo "---"
# Confirm whether core-api/package.json (or others) is required for a frozen install at /app
fd -HI 'package.json' -d 2

Repository: oasm-platform/open-asm

Length of output: 648

Copy the core-api manifest before the frozen workspace install

pnpm-workspace.yaml includes both core-api and console, but this stage only copies console/package.json before pnpm install --frozen-lockfile. Add core-api/package.json as well so the workspace install resolves consistently.

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@console/Dockerfile` around lines 15 - 20, The frozen workspace install in the
console Docker build is missing the core-api workspace manifest, so pnpm cannot
resolve the full workspace consistently. Update the Dockerfile copy step used
before the pnpm install --frozen-lockfile command to include
core-api/package.json alongside console/package.json, keeping the workspace
manifests in sync for the install stage.


COPY . .
RUN bun install
# Copy console source code
COPY console/ ./console/

# Build
RUN \
VITE_API_URL=APP_VITE_API_URL \
bun run build
pnpm --filter console run build

# Clean bun cache and remove unused files
RUN bun pm cache clean && rm -rf src test
# Clean source and unused files
RUN rm -rf src test

FROM nginx:stable-alpine

COPY --from=builder /app/dist /usr/share/nginx/html
COPY ./nginx.conf /etc/nginx/conf.d/default.conf
COPY --from=builder /app/console/dist /usr/share/nginx/html
COPY ./console/nginx.conf /etc/nginx/conf.d/default.conf
EXPOSE 80
CMD ["nginx", "-g", "daemon off;"]
CMD ["nginx", "-g", "daemon off;"]
6 changes: 3 additions & 3 deletions console/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@
"build": "tsc -b && vite build",
"lint": "eslint .",
"preview": "vite preview",
"gen:api": "npx orval",
"gen:api": "orval",
"test": "vitest",
"test:run": "vitest run",
"test:coverage": "vitest run --coverage",
Expand All @@ -17,8 +17,7 @@
"e2e:ui": "playwright test --config=e2e/playwright.config.ts --ui",
"e2e:headed": "playwright test --config=e2e/playwright.config.ts --headed",
"e2e:debug": "playwright test --config=e2e/playwright.config.ts --debug",
"test:all": "npm run test:run && npm run e2e",
"prepare": "husky"
"test:all": "npm run test:run && npm run e2e"
},
"dependencies": {
"@ai-sdk/react": "^3.0.146",
Expand Down Expand Up @@ -72,6 +71,7 @@
"echarts-for-react": "^3.0.6",
"embla-carousel-react": "^8.6.0",
"framer-motion": "^12.23.12",
"leaflet": "^1.9.4",
"lucide-react": "^1.14.0",
"media-chrome": "^4.18.3",
"motion": "^12.38.0",
Expand Down
Loading
Loading