@fullcalendar/core 5.10.1
Provides core functionality, including the Calendar class
@fullcalendar/core@5.10.1 was published on 2021-11-03. Its manifest declares 3 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 @fullcalendar/core versions · Permanent reference to 5.10.1 · View npm registry JSON · Latest release
Package specifications
| Version | 5.10.1 |
|---|---|
| License declaration | MIT |
| Published | 2021-11-03T04:09:05.785Z |
| Node.js requirement | Not declared |
| Type declarations | Bundled declarations |
| Runtime dependency count | 3 |
| Peer requirement count | 0 |
| Optional dependency count | 0 |
| Minified size | Measurement not available yet |
| Minified + gzip | Measurement not available yet |
| Unpacked distribution size | 867.61 KiB |
| Published file count | 250 |
| Package type | Not declared |
| ES module entry | main.js |
| Default entry | main.cjs.js |
| Side effects declaration | true |
| Direct advisories | 0 |
| Resolved graph dependencies | 3 |
| Repository stars | Unknown |
| Repository forks | Unknown |
Install @fullcalendar/core 5.10.1
npm install @fullcalendar/core@5.10.1 pnpm add @fullcalendar/core@5.10.1 yarn add @fullcalendar/core@5.10.1
Runtime dependencies
- tslib ^2.1.0
- preact ^10.0.5
- @fullcalendar/common ~5.10.1
Peer requirements
- None declared
Optional dependencies
- None declared
Resolved dependency graph
This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.
- @fullcalendar/common@5.10.1 — direct
- preact@10.29.8 — direct
- tslib@2.9.1 — direct
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-01T15:26:45.481Z
- https://api.deps.dev/v3/systems/npm/packages/%40fullcalendar%2Fcore/versions/5.10.1 — retrieved 2026-11-01T15:26:45.910Z
- https://api.deps.dev/v3/systems/npm/packages/%40fullcalendar%2Fcore/versions/5.10.1:dependencies — retrieved 2026-11-01T15:26:45.952Z