Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 10 additions & 2 deletions package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@zenstackhq/proxy",
"version": "0.2.4",
"version": "0.2.5",
"description": "A CLI tool to run an Express server that proxies CRUD requests to a ZenStack backend",
"main": "index.js",
"publishConfig": {
Expand All @@ -12,7 +12,9 @@
"url": "https://github.com/zenstackhq/proxy"
},
"bin": {
"zenstack-proxy": "./bin/cli.js"
"zenstack-proxy": "./bin/cli.js",
"zenstack-studio": "./bin/cli.js",
"zen-studio": "./bin/cli.js"
},
Comment on lines +15 to 18
Copy link

Copilot AI Jan 26, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 uses AI. Check for mistakes.
"scripts": {
"clean": "rimraf dist",
Comment on lines +15 to 20
Copy link

Copilot AI Jan 26, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 uses AI. Check for mistakes.
Expand Down Expand Up @@ -44,5 +46,11 @@
"copyfiles": "^2.4.1",
"rimraf": "^4.0.0",
"typescript": "^5.0.0"
},
"exports": {
".": {
"import": "./index.js",
"require": "./index.js"
}
Copy link

Copilot AI Jan 26, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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"

Copilot uses AI. Check for mistakes.
}
}