npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

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

v5.0.4

Published

The module for storing test editor bundles for CKEditor Cloud Services

Readme

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

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

Adding a new bundle

  1. Duplicate a bundle in src/editors. The name of a directory will be used as a name of the bundle.
  2. Adjust packages, versions and plugins in the new bundle.
  3. Include new bundle in exported object in index.js.
  4. Build all bundles with pnpm build:bundles.
  5. 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.

  1. Use Publish token in ~/.npmrc file.
  2. 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
  1. Make sure that all bundles are built and available in src/bundles directory.
  2. Run npm publish.
  3. Revert version to 1.0.0 and set private to true in the package.json file.
  4. Use the Read-only token back in ~/.npmrc file.