@stackbit/cms-core 0.1.26-staging.0
stackbit-dev
@stackbit/cms-core@0.1.26-staging.0 was published on 2023-03-14. Its manifest declares 19 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.
All @stackbit/cms-core versions · Permanent reference to 0.1.26-staging.0 · View npm registry JSON · Latest release
Package specifications
| Version | 0.1.26-staging.0 |
|---|---|
| License declaration | MIT |
| Published | 2023-03-14T09:05:23.274Z |
| Node.js requirement | Not declared |
| Type declarations | Bundled declarations |
| Runtime dependency count | 19 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 875.91 KiB |
| Published file count | 157 |
| Package type | Not declared |
| ES module entry | Not declared |
| Default entry | dist/index.js |
| Side effects declaration | Not declared |
| Direct advisories | Unknown |
| Resolved graph dependencies | Unknown |
| Repository stars | Unknown |
| Repository forks | Unknown |
Install @stackbit/cms-core 0.1.26-staging.0
npm install @stackbit/cms-core@0.1.26-staging.0 pnpm add @stackbit/cms-core@0.1.26-staging.0 yarn add @stackbit/cms-core@0.1.26-staging.0
Runtime dependencies
- esm ^3.2.25
- glob ^7.1.6
- uuid ^9.0.0
- chalk ^4.0.1
- lodash ^4.17.20
- moment ^2.29.1
- parse5 ^6.0.1
- js-yaml ^3.13.1
- slugify ^1.6.5
- fs-extra ^8.1.0
- htmlparser ^1.7.7
- micromatch ^4.0.2
- @iarna/toml ^2.2.3
- @babel/parser ^7.11.5
- @stackbit/sdk 0.3.19-staging.0
- @babel/traverse ^7.11.5
- @stackbit/types 0.1.11-staging.0
- @stackbit/utils 0.2.18-staging.0
- sanitize-filename ^1.6.3
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-01T14:41:24.861Z