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

@commonapp/ckeditor5-build-classic

v2.5.0

Published

Common App fork of CKEditor 5

Downloads

92

Readme

Common App CKEditor

A fork of CKEditor 5 for usage within the Common App product suite.

Build and publish instructions

  1. Create feature branch off of develop
  2. Complete any feature work and bump package.json version appropriately according to semantic versioning
  3. Open a pull request against develop
  4. Once merged, publish to npm:
    1. Run npm install to ensure you have the latest dependencies
    2. Run npm run build
    3. If build succeeds, run npm publish
      • Depending on permissions, a senior developer may need to assist with this
      • It requires npm publishing permissions and a local login to the account with those permissions
  5. npm will email the publisher when the new version is live

After publishing the new version to npm, go back into the product being worked on and bump the package.json file version for @commonapp/cackeditor to the new version.

Use the specific version instead of the loose version globbing to prevent breaking changes from being pushed in future updates.