fix: copy shared package dist into service node_modules in production Dockerfiles - #33
Conversation
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (6)
✨ Finishing Touches🧪 Generate unit tests (beta)
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
Fixes the production Docker images for all six microservices so the
@transit-tracker/sharedpackage is available at runtime.Problem
The shared package is a local workspace dependency resolved via symlinks during development, but those symlinks don't exist inside the production Docker image, causing module resolution failures at startup.
Fix
In the production stage of each service Dockerfile, explicitly copy the built shared package into the service's
node_modules/@transit-tracker/shared:Affects:
agencies,alerts,ingestion,routes,stops,vehicles