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 🙏

© 2024 – Pkg Stats / Ryan Hefner

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

v4.0.0

Published

The module for storing test editor bundles for CKEditor Cloud Services

Downloads

4,223

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

jflakus-cksourcejflakus-cksourcelekarev.tinylekarev.tinyfinn-but-like-really-tiny-onefinn-but-like-really-tiny-onejankantyjankantypmazurek-cksourcepmazurek-cksourcejugglingjsons-cksourcejugglingjsons-cksourcenoxuhax.tinynoxuhax.tinysdudzik-cksourcesdudzik-cksourcekorobochkinkorobochkinyacodesyacodesrinat.khusyainovrinat.khusyainovilia-sidorov-tinyilia-sidorov-tinyigor-kuznetsovigor-kuznetsovdimakovalevskydimakovalevskyp.wiadernyp.wiadernylukaszgudellukaszgudelmhartwich-cksourcemhartwich-cksourcelkaletalkaletarpotyka-cksourcerpotyka-cksourcempytel-cksourcempytel-cksourcedszczepaniak-cksourcedszczepaniak-cksourcesmarkowicz-cksourcesmarkowicz-cksourcebartoszputekbartoszputekbartekczerwonkabartekczerwonkasdomassdomasd.pawlowski.cksourced.pawlowski.cksources.greczyns.greczynp.miszczakp.miszczakkacper.betanskikacper.betanski

Keywords

Readme

CKEditor test bundles module

The bundle contains CKEditor 5 builds used for E2E and CKEditor Documents Converter tests. All the available bundles can be found in index.js.

Table of contents

  • CKEditor 5 builds defined in scripts/updateCKEditorBundles.js in version 40.1.0,
  • Track Changes Data Editor - built manually. The bundle have been provided to make sure integration with TrackChangesData plugin works correctly,
  • Collaboration Editor V32 - built manually. Before CKEditor5 v33 RTC plugins contained their offline versions so to make sure CS is backward compatible this bundle is provided. The actual version is 27.0.0
  • Multi-root Editor - built manually. It's a bundle with all RTC features (RTC, Comments, Track Changes, Revision History) and support for multi-root. Multi-root editors can't be built using the Online Builder.
  • Collaboration Editor DLL - built manually. DLL editors cannot be built through the Online Builder. For instructions on how to build such editor see https://www.notion.so/How-to-upload-the-DLL-editor-bundle-to-CS-91856b2d7633491e8f123a2c18d6c25f
  • Classic Editor DLL - built manually similarly as the one above.

How to update CKEditor test bundles

  1. Copy bundles directory from some package that currently has installed newest @cksource-cs/ckeditor-test-bundles-module NPM package (e.g. cs/cs-e2e-tests/node_modules/@cksource-cs/ckeditor-test-bundles-module/src/bundles) to your local machine (it is required to add missing bundles in step 3).
  2. Run npm run update:bundles.
  3. Add missing bundles - collaboration-editor-v32.bundle,multiroot-editor.bundle, classic-editor-dll.bundle, collaboration-editor-dll.bundle and track-changes-data-editor.bundle from your local copy. Eventually, you can get them from pulled tarball from npm from the latest version of the package.
  4. Set a proper version, lastPublicVersion and set private to false in the package.json file.
  5. update editorVersion in package.json file.
  6. Run npm publish (use temporarily Publish token in ~/.npmrc file).

How to add a new bundle

  1. Define a new bundle and its set of plugins in scripts/updateCKEditorBundles.js.
  2. Run npm run update:bundles.
  3. Set a proper version, lastPublicVersion and set private to false in the package.json file.
  4. Run npm publish (use temporarily Publish token in ~/.npmrc file).

After publish do not forget to:

  • update @cksource-cs/ckeditor-test-bundles-module in packages where the package is used,
  • 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.