-
-
Notifications
You must be signed in to change notification settings - Fork 0
chore: add export without export package.json so that zenstack CLI wouldn't check the version of it #22
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
…uldn't check the version of it
📝 WalkthroughWalkthroughVersion bumped to 0.2.5. Two new CLI bin aliases added ( Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 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 |
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 updates the published package metadata to better control how @zenstackhq/proxy is consumed, and adds additional CLI entrypoints.
Changes:
- Bump package version to
0.2.5. - Add additional
binaliases (zenstack-studio,zen-studio) pointing to the existing CLI. - Add an
exportsmap that only exports the package root entrypoint (and does not exportpackage.json).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "zenstack-proxy": "./bin/cli.js", | ||
| "zenstack-studio": "./bin/cli.js", | ||
| "zen-studio": "./bin/cli.js" |
Copilot
AI
Jan 26, 2026
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.
The new bin aliases ("zenstack-studio" / "zen-studio") both point to the same CLI entrypoint, but the CLI currently hard-codes its displayed command name to "zenstack-proxy". When users run zenstack-studio --help they'll still see zenstack-proxy in usage/help output, which is confusing. Consider either adding small wrapper bin scripts per command name, or updating the CLI to derive program.name() from process.argv[1] so each alias displays correctly.
| "zenstack-proxy": "./bin/cli.js", | |
| "zenstack-studio": "./bin/cli.js", | |
| "zen-studio": "./bin/cli.js" | |
| "zenstack-proxy": "./bin/cli.js" |
bump version
Summary by CodeRabbit
New Features
Chores
✏️ Tip: You can customize this high-level summary in your review settings.