chore: add export without export package.json so that zenstack CLI wouldn't check the version of it

[jiashengguo]

Summary by CodeRabbit

• New Features

  • Added new CLI command aliases zenstack-studio and zen-studio for convenient access to the studio.

• Chores

  • Bumped version to 0.2.5.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

Version bump from 0.2.4 to 0.2.5 with the addition of two new CLI command aliases (zenstack-studio and zen-studio) and a top-level exports field establishing module entry points in package.json.

Changes

Cohort / File(s)	Summary
Package Configuration package.json	Version update (0.2.4 → 0.2.5), two new CLI aliases added to bin section, top-level exports field introduced mapping "." to index.js for both import and require

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• chore: add export without export package.json so that zenstack CLI wouldn't check the version of it #22: Applies identical package.json modifications across both repositories including version bump, new bin aliases, and top-level exports mapping.

Suggested reviewers

• Copilot

Poem

🐰 A version hop to point-two-five so bright,
New CLI names dance into sight,
zenstack-studio, zen-studio too,
With exports mapped, the package brand new!

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

Updates the published package metadata to add an exports map (without exporting package.json) and add additional CLI entrypoints.

Changes:

• Bump package version to 0.2.5.
• Add new bin aliases (zenstack-studio, zen-studio) pointing to the existing CLI.
• Add an exports map for the package root entrypoint.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Adding new bin aliases (zenstack-studio, zen-studio) will install additional executables. Right now the CLI code hard-codes the program name/description to zenstack-proxy, so running these new binaries will show incorrect help/output and may confuse users. Consider either (a) making the CLI name dynamic based on the invoked command, or (b) pointing these aliases at wrappers that set the intended command name/behavior.

Suggested change

	"zenstack-proxy": "./bin/cli.js",
	"zenstack-studio": "./bin/cli.js",
	"zen-studio": "./bin/cli.js"
	},
	"zenstack-proxy": "./bin/cli.js"
	},

[Copilot]

The new bin entries are a user-facing change, but the README currently documents only zenstack-proxy. If zenstack-studio / zen-studio are intended to be supported entrypoints (not just internal compatibility shims), the usage docs should be updated accordingly to avoid confusion.

Suggested change

	"zenstack-proxy": "./bin/cli.js",
	"zenstack-studio": "./bin/cli.js",
	"zen-studio": "./bin/cli.js"
	},
	"scripts": {
	"clean": "rimraf dist",
	"zenstack-proxy": "./bin/cli.js"
	},
	"scripts": {
	"clean": "rimraf dist",
	"scripts": {
	"clean": "rimraf dist",

[Copilot]

Adding an exports map without exporting ./package.json will make require('@zenstackhq/proxy/package.json') (and similar tooling) fail with ERR_PACKAGE_PATH_NOT_EXPORTED. If this is intentional, it’s a breaking change worth calling out (and potentially warrants more than a patch bump); if not intentional, add an explicit "./package.json" export or provide another supported way for consumers/tools to read the version.

Suggested change

	}
	},
	"./package.json": "./package.json"