Skip to content

Fix Waku production startup after pruning dev dependencies - #170

Open
jay23606 wants to merge 1 commit into
fly-apps:mainfrom
jay23606:fix/166-waku-standalone-server
Open

jay23606 wants to merge 1 commit into
fly-apps:mainfrom
jay23606:fix/166-waku-standalone-server

Conversation

@jay23606

Copy link
Copy Markdown

Fixes #166

Waku's production build emits dist/serve-node.js, which can run without the dev dependencies that npm prune --omit=dev removes. Detect Waku projects, start the generated server directly with Node, and set PORT=3000 for the production server.

Validation:

  • Regression test on clean base ff76b14: failed as expected (Waku detection, start command, and deploy PORT).
  • Same regression test on this branch: 3 passing.
  • npx mocha test/gdf.test.js --timeout 10000 --grep "gdf: .dockerignore" --invert: 153 passing, 4 pending.
  • npm run eslint: passed.
  • The three .dockerignore tests fail on both clean base and this checkout under WSL; the full suite was not verified.
  • Container build and live Waku runtime were not verified.

🤖 Generated with Claude Code

Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
Signed-off-by: jay23606 <4602056+jay23606@users.noreply.github.com>
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.

Waku: waku start needs dev dependencies, which the prune removes

1 participant