@sanity/validation 6.20.0-next.41
Document validation for Sanity schemas
@sanity/validation@6.20.0-next.41 was published on 2026-10-15. Its manifest declares 9 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=22.12.
All @sanity/validation versions · Permanent reference to 6.20.0-next.41 · View npm registry JSON · Latest release
Package specifications
| Version | 6.20.0-next.41 |
|---|---|
| License declaration | MIT |
| Published | 2026-10-15T14:17:16.610Z |
| Node.js requirement | >=22.12 |
| Type declarations | Bundled declarations |
| Runtime dependency count | 9 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 213.09 KiB |
| Published file count | 11 |
| Package type | module |
| ES module entry | Not declared |
| Default entry | Not declared |
| Side effects declaration | false |
| Direct advisories | Unknown |
| Resolved graph dependencies | Unknown |
| Repository stars | Unknown |
| Repository forks | Unknown |
Install @sanity/validation 6.20.0-next.41
npm install @sanity/validation@6.20.0-next.41 pnpm add @sanity/validation@6.20.0-next.41 yarn add @sanity/validation@6.20.0-next.41
Runtime dependencies
- rxjs ^7.8.2
- dequal ^2.0.3
- i18next ^26.4.4
- lodash-es ^4.18.1
- @sanity/util 6.20.0-next.41+549aa73eff
- @sanity/types 6.20.0-next.41+549aa73eff
- @sanity/client ^8.9.0
- @sanity/schema 6.20.0-next.41+549aa73eff
- @sanity/id-utils ^1.1.0
Peer requirements
- None declared
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:29:55.908Z