🚀 Big News:Socket Has Acquired Secure Annex.Learn More
Socket
Book a DemoSign in
Socket

@cksource-cs/ckeditor-test-bundles-module

Package Overview
Dependencies
Maintainers
53
Versions
29
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@cksource-cs/ckeditor-test-bundles-module

The module for storing test editor bundles for CKEditor Cloud Services

latest
Source
npmnpm
Version
6.0.0
Version published
Weekly downloads
1.6K
-4.01%
Maintainers
53
Weekly downloads
 
Created
Source

CKEditor test bundles module

The module contains CKEditor 5 builds used for E2E and CKEditor Documents Converter tests. All the available bundles can be found in index.js. All bundles can be built locally with webpack (or other build tools) and all bundles include their own plugin configuration.

Updating CKEditor test bundles

  • Find the bundle(s) that you want to update.
  • Change version of packages in package.json or adjust the plugins in bundles.
  • Build all bundles with pnpm build:bundles.
  • Release new version of ckeditor-test-bundles module.

Adding a new bundle

  • Duplicate a bundle in src/editors. The name of a directory will be used as a name of the bundle.
  • Adjust packages, versions and plugins in the new bundle.
  • Include new bundle in exported object in index.js.
  • Build all bundles with pnpm build:bundles.
  • Release new version of ckeditor-test-bundles module.

Releasing new version of module

Publish token is different from the one used for daily development purposes. You can generate it in your npm account dashboard.

  • Use Publish token in ~/.npmrc file.
  • In the package.json file, set:
  • a proper version (updated lastPublicVersion) :

version should stay at 1.0.0 in git. You should change the version temporarily to for example: 5.0.1 (or 5.1.0/6.0.0 depending on semver) and once you release this module change the lastPublicVersion to the released one and revert version change back to 1.0.0 - after merging lastPublicVersion should be the same as the latest version on npm

  • lastPublicVersion
  • set private to false
  • Make sure that all bundles are built and available in src/bundles directory.
  • Run npm publish.
  • Revert version to 1.0.0 and set private to true in the package.json file.
  • Use the Read-only token back in ~/.npmrc file.

FAQs

Package last updated on 15 Apr 2026

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts