qa(fleet-launch): force devDeps in dev install so paperclip :3100 boots under NODE_ENV=production#44
Merged
Conversation
…oots under NODE_ENV=production The dev launch path (`pnpm dev` / `pnpm dev:paperclip`) ran `pnpm install --prefer-offline` for the packages/core workspace. Under an ambient NODE_ENV=production, pnpm skips devDependencies, so typescript is never installed into packages/core and `tsc` is absent. The paperclip dev-runner builds the plugin SDK (@paperclipai/shared -> `tsc`) before starting the server; that build dies with `sh: tsc: command not found` and the orchestrator never binds :3100 — blocking fleet ignition. Add `--prod=false` to the two dev-time installs (`dev` and `dev:paperclip:install`) so the dev workflow always installs devDeps regardless of ambient NODE_ENV. Verified: with NODE_ENV=production set, the patched install keeps tsc present and :3100 boots. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes the launch-blocking failure that prevented the Paperclip orchestrator (
:3100) from booting, which blocks fleet ignition.The dev launch path (
pnpm dev/pnpm dev:paperclip) installs thepackages/coreworkspace withpnpm install --prefer-offline. Under an ambientNODE_ENV=production, pnpm skips devDependencies, sotypescriptis never installed intopackages/coreandtscis missing. The paperclip dev-runner builds the plugin SDK (@paperclipai/shared→tsc) before starting the server; that build dies withsh: tsc: command not found, the dev-runner aborts, and:3100never binds.Fix
Add
--prod=falseto the two dev-time installs so dev always pulls devDeps regardless of ambientNODE_ENV:package.jsondev:pnpm install --prefer-offline→--prefer-offline --prod=falsepackage.jsondev:paperclip:install: sameFindings digest
node→env: node: No such file or directory; token refresh_failed); it was not keeping:3100up. Out of scope for this PR.NODE_ENV=production→ dev install skips devDeps → notsc→ plugin-sdk build fails →:3100boot aborts.Verification
NODE_ENV=production bash -c 'cd packages/core && pnpm install --prefer-offline --prod=false'→ exit 0,tscpresent inpackages/coreandpackages/core/packages/shared.:3100(server listening, DB migrated, Agent JWT set, wavex plugin v0.15.0 activated).Fleet ignited (on this branch's fix)
tony-apple-qa(paperclipc293df60-…, prefixWAVAAAA), goal MRR 5k→15k/90d.model: claude-sonnet-4-6, resumed (paused→idle); heartbeat scheduler enqueuing runs (heartbeat timer tick enqueued runs {checked:16,enqueued:16}); agents executing.Changed files
package.json(+2/-2)Deliverable
.plateau-agency/deliverables/fleet-launch/—report.md,screenshots/(dashboard PNG + fleet-agents-state.json + console-evidence.txt),logs/. Fleet signal at.plateau-agency/meters/fleet.ready.🤖 Generated with Claude Code