@ckeditor/ckeditor-cloud-services-collaboration 32.0.0

CKEditor Cloud Services Collaboration low-level API is required by CKEditor 5 Collaboration features to enable real-time collaborative editing within the CKEditor 5.

@ckeditor/ckeditor-cloud-services-collaboration@32.0.0 was published on 2022-05-25. Its manifest declares 6 runtime dependencies and 0 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All @ckeditor/ckeditor-cloud-services-collaboration versions · Permanent reference to 32.0.0 · Latest release

Package specifications

Version32.0.0
License declarationSEE LICENSE IN LICENSE.md
Published2022-05-25T11:17:52.935Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count6
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size288.92 KiB
Published file count96
Package typeNot declared
ES module entryNot declared
Default entrydist/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies47
Repository starsUnknown
Repository forksUnknown

Install @ckeditor/ckeditor-cloud-services-collaboration 32.0.0

npm install @ckeditor/ckeditor-cloud-services-collaboration@32.0.0
pnpm add @ckeditor/ckeditor-cloud-services-collaboration@32.0.0
yarn add @ckeditor/ckeditor-cloud-services-collaboration@32.0.0

Runtime dependencies

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.

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