@ckeditor/ckeditor-cloud-services-collaboration 48.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@48.0.0 was published on 2023-06-28. Its manifest declares 6 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=8.0.0.

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

Package specifications

Version48.0.0
License declarationSEE LICENSE IN LICENSE.md
Published2023-06-28T07:47:26.018Z
Node.js requirement>=8.0.0
Type declarationsBundled declarations
Runtime dependency count6
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size775.43 KiB
Published file count209
Package typeNot declared
ES module entryNot declared
Default entrysrc/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies47
Repository starsUnknown
Repository forksUnknown

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

npm install @ckeditor/ckeditor-cloud-services-collaboration@48.0.0
pnpm add @ckeditor/ckeditor-cloud-services-collaboration@48.0.0
yarn add @ckeditor/ckeditor-cloud-services-collaboration@48.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