fix(ambient-ui): fix Docker build for standalone output#1619
Conversation
- Build SDK dist in Docker (ts-sdk dist/ is gitignored) - Copy standalone output from correct nested path (outputFileTracingRoot nests under components/ambient-ui/) - Use webpack for production build (Turbopack can't resolve file: deps) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
✅ Deploy Preview for cheerful-kitten-f556a0 canceled.
|
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
Cache: Disabled due to data retention organization setting Knowledge base: Disabled due to data retention organization setting 📝 WalkthroughWalkthroughBuilder stage in ChangesBuilder Output Packaging
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
dist/in Docker (ts-sdkdist/is gitignored, CI has no pre-built output)outputFileTracingRootnests files undercomponents/ambient-ui/)file:linked dependencies)Fixes the
Cannot find module '/app/server.js'crash at container startup and theModule not found: Can't resolve 'ambient-sdk'build failure.Test plan
npm run buildpasses locally with webpackserver.jsconfirmed at.next/standalone/components/ambient-ui/server.jsMODULE_NOT_FOUNDerror🤖 Generated with Claude Code
Summary by CodeRabbit