-
Notifications
You must be signed in to change notification settings - Fork 247
chore: make private deps of data-service public #7593
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR makes three internal packages public by replacing the "private": true field with publishConfig settings. This change is necessary because these packages are transitive dependencies of the VS Code extension that were inadvertently made private in a previous refactoring.
- Removes private flag from compass-utils, compass-logging, and compass-app-registry
- Adds publishConfig with public access to enable npm publishing
- Corrects dependency visibility for VS Code extension compatibility
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| packages/compass-utils/package.json | Changed from private to public with publishConfig |
| packages/compass-logging/package.json | Changed from private to public with publishConfig |
| packages/compass-app-registry/package.json | Changed from private to public with publishConfig |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "publishConfig": { | ||
| "access": "public" | ||
| }, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you give an example where it's pulled as transitive for other public packges? We should probably remove this dependency
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| "@mongodb-js/compass-app-registry": "^9.4.28", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Le Roux Bodenstein
11:26
| "@mongodb-js/compass-app-registry": "^9.4.28", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, I guess it's weird that DataService depends on compass-logging and not on something lower level like mongodb log writer (I'm sure I said something exactly opposite at some point 🙂). I'll open a ticket for that
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| import { createServiceLocator } from '@mongodb-js/compass-app-registry'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems easy enough: #7595
gribnoysup
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good as a temp workaround, but I opened https://jira.mongodb.org/browse/COMPASS-10116 to follow-up
We missed some transitive deps of things the vscode extension depend on when we made a bunch of packages private recently.