fix: add explicit export entries for community forge adapters#1041
fix: add explicit export entries for community forge adapters#1041
Conversation
bun build --compile cannot resolve deep subpath imports through wildcard export maps. Adding explicit entries for gitea and gitlab adapter paths fixes binary builds.
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughAdded explicit subpath exports for Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
✨ 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 |
…00#1041) bun build --compile cannot resolve deep subpath imports through wildcard export maps. Adding explicit entries for gitea and gitlab adapter paths fixes binary builds.
…00#1041) bun build --compile cannot resolve deep subpath imports through wildcard export maps. Adding explicit entries for gitea and gitlab adapter paths fixes binary builds.
Summary
bun build --compilecannot resolve@archon/adapters/community/forge/giteaand@archon/adapters/community/forge/gitlabthrough the wildcard export mappackages/adapters/package.jsonfor the deep subpaths"./*"is kept for all other subpath importsUX Journey
Before
After
Architecture Diagram
N/A — no architectural change, just a package.json exports fix.
Label Snapshot
risk: lowsize: XSadaptersadapters:exportsChange Metadata
fixadaptersLinked Issue
Validation Evidence (required)
Security Impact (required)
Compatibility / Migration
Human Verification (required)
versioncommand, confirmed update notice works--quietsuppression, cached vs fresh fetchSide Effects / Blast Radius (required)
Rollback Plan (required)
Risks and Mitigations
Summary by CodeRabbit