@sanity/resolver 0.126.0-next.febffa69
Resolves parts and plugins from a Sanity configuration
@sanity/resolver@0.126.0-next.febffa69 was published on 2018-03-02. Its manifest declares 6 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. The declared Node.js requirement is >=6.0.0.
All @sanity/resolver versions · Permanent reference to 0.126.0-next.febffa69 · View npm registry JSON · Latest release
Package specifications
| Version | 0.126.0-next.febffa69 |
|---|---|
| License declaration | MIT |
| Published | 2018-03-02T08:35:11.626Z |
| Node.js requirement | >=6.0.0 |
| Type declarations | Not declared |
| Runtime dependency count | 6 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 55.90 KiB |
| Published file count | 20 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | lib/resolver.js |
| Side effects declaration | Not declared |
| Direct advisories | 0 |
| Resolved graph dependencies | Unknown |
| Repository stars | Unknown |
| Repository forks | Unknown |
Install @sanity/resolver 0.126.0-next.febffa69
npm install @sanity/resolver@0.126.0-next.febffa69 pnpm add @sanity/resolver@0.126.0-next.febffa69 yarn add @sanity/resolver@0.126.0-next.febffa69
Runtime dependencies
- lodash ^4.17.4
- fs-extra ^5.0.0
- path-exists ^3.0.0
- @sanity/util 0.126.0-next.febffa69
- promise-props-recursive ^1.0.0
- @sanity/generate-help-url 0.126.0-next.febffa69
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-01T22:19:51.350Z
- https://api.deps.dev/v3/systems/npm/packages/%40sanity%2Fresolver/versions/0.126.0-next.febffa69 — retrieved 2026-11-01T22:19:51.747Z