Skip to content

refactor(cli): replace semver usage with verkit - #2837

Open
liangmiQwQ wants to merge 1 commit into
voidzero-dev:mainfrom
liangmiQwQ:liang/codex/migrate-verkit
Open

liangmiQwQ wants to merge 1 commit into
voidzero-dev:mainfrom
liangmiQwQ:liang/codex/migrate-verkit

Conversation

@liangmiQwQ

@liangmiQwQ liangmiQwQ commented Sep 27, 2026 •

Copy link
Copy Markdown
Collaborator

This PR replaces direct semver usage in the CLI and repository tools with verkit (made by @ sxzz). Named ESM imports let the CLI build tree-shake unused version APIs. Building Vite+ with pnpm -F vite-plus build-ts before and after this change reduces the combined size of packages/cli/dist/*.js by 26,079 B (from 1,303,781 B to 1,277,702 B, uncompressed).

Built-in TypeScript declarations remove the direct @types/semver dependency. Range handling now uses rangeToComparators instead of reading Range internals, and coerced versions use plain records, making the call sites easier to maintain. Existing prerelease options are preserved; the core package retains semver for bundled upstream consumers.

🤖 Generated with Codex

@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addednpm/​verkit@​0.5.010010010089100

View full report

@liangmiQwQ
liangmiQwQ marked this pull request as ready for review September 27, 2026 13:48
@liangmiQwQ liangmiQwQ changed the title refactor(cli): replace direct semver usage with verkit refactor(cli): replace semver usage with verkit Sep 27, 2026
@liangmiQwQ

Copy link
Copy Markdown
Collaborator Author

cc @sxzz

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant