@sanity/cli 4.10.0-next.57
Sanity CLI tool for managing Sanity installations, managing plugins, schemas and datasets
@sanity/cli@4.10.0-next.57 was published on 2025-09-23. Its manifest declares 15 runtime dependencies and 1 peer requirement. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=20.19 <22 || >=22.12.
All @sanity/cli versions · Permanent reference to 4.10.0-next.57 · View npm registry JSON · Latest release
Package specifications
| Version | 4.10.0-next.57 |
|---|---|
| License declaration | MIT |
| Published | 2025-09-23T10:36:47.591Z |
| Node.js requirement | >=20.19 <22 || >=22.12 |
| Type declarations | Bundled declarations |
| Runtime dependency count | 15 |
| Peer requirement count | 1 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 10785.34 KiB |
| Published file count | 214 |
| Package type | commonjs |
| ES module entry | ./lib/index.mjs |
| Default entry | ./lib/index.js |
| Side effects declaration | false |
| Direct advisories | Unknown |
| Resolved graph dependencies | Unknown |
| Repository stars | Unknown |
| Repository forks | Unknown |
Install @sanity/cli 4.10.0-next.57
npm install @sanity/cli@4.10.0-next.57 pnpm add @sanity/cli@4.10.0-next.57 yarn add @sanity/cli@4.10.0-next.57
Runtime dependencies
- chalk ^4.1.2
- debug ^4.4.1
- get-it ^8.6.10
- semver ^7.7.2
- esbuild 0.25.10
- groq-js ^1.18.0
- pkg-dir ^5.0.0
- prettier ^3.5.3
- @sanity/client ^7.11.2
- @babel/traverse ^7.28.4
- @sanity/codegen 4.10.0-next.57+4d26a51ac3
- esbuild-register ^3.6.0
- @sanity/telemetry ^0.8.0
- @sanity/runtime-cli ^10.6.1
- @sanity/template-validator ^2.4.3
Peer requirements
- babel-plugin-react-compiler * (optional peer)
Optional dependencies
- None declared
How to interpret the specifications
Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.
Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.
Evidence and freshness
- Readable npm registry JSON — retrieved 2026-11-01T17:18:44.191Z