Skip to content

Fix missing @vercel/ncc dependency in subdirectory builds#17

Open
rippleitinnz wants to merge 1 commit into
reputation-testingfrom
rippleitinnz-fix/missing-ncc-dependency-gp
Open

Fix missing @vercel/ncc dependency in subdirectory builds#17
rippleitinnz wants to merge 1 commit into
reputation-testingfrom
rippleitinnz-fix/missing-ncc-dependency-gp

Conversation

@rippleitinnz

Copy link
Copy Markdown

Problem

The npm run bundle command fails when building from a fresh clone because the lobby and gp-port-server subdirectories use npx ncc without having @vercel/ncc as a dependency.

Error encountered: npm error could not determine executable to run

Root Cause

The main package.json includes @vercel/ncc, but the subdirectories that use npx ncc build in their build scripts don't have it listed as a dependency.

Solution

Add @vercel/ncc v0.34.0 (matching main package.json version) to dependencies in:

  • dependencies/lobby/package.json
  • dependencies/gp-port-server/package.json

Testing

  • Verified npm run bundle now completes successfully in fresh environments
  • Confirmed Docker containerized builds work without manual dependency installation
  • No impact on existing functionality

Impact

Enables reliable builds from fresh clones and containerized environments without requiring manual setup steps.

## Problem
The `npm run bundle` command fails when building from a fresh clone because the lobby and gp-port-server subdirectories use `npx ncc` without having @vercel/ncc as a dependency.

Error encountered: npm error could not determine executable to run

## Root Cause
The main package.json includes @vercel/ncc, but the subdirectories that use `npx ncc build` in their build scripts don't have it listed as a dependency.

## Solution
Add @vercel/ncc v0.34.0 (matching main package.json version) to dependencies in:
- dependencies/lobby/package.json  
- dependencies/gp-port-server/package.json

## Testing
- Verified `npm run bundle` now completes successfully in fresh environments
- Confirmed Docker containerized builds work without manual dependency installation
- No impact on existing functionality

## Impact
Enables reliable builds from fresh clones and containerized environments without requiring manual setup steps.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant