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

@mitodl/ckeditor-custom-build

v0.0.4

Published

MIT Open Learning custom build of CKEditor5

Downloads

43

Readme

OL CKEditor5 Custom Build

This is our custom build for CKEditor5. It's forked from their 'classic' build (here).

Development setup

Install the deps with yarn install. Then if you want to check out the editor you can do npm start and visit localhost:8080 to see a development build of the editor with an example document. There's both an editable and a read-only example.

Remember to npm run fmt and npm run lint!

Building and publishing

You can run npm run build to run the webpack build. If you want to test the integration with another project, like open-discussions, you can do the following:

In this repo:

npm run build
rm -rf *.tgz
npm pack

This will create a .tgz just like what would be pushed to the npm registry, but without publishing anything. We can use this in other projects to try out installing the package without having to push a new version up to npm.

To use it, copy the .tgz file to your local clone of the open-discussions (or other project) repo and run:

docker-compose run watch yarn add ./name-of-the-file.tgz

This will add the .tgz file in such a way that looks, to node, like a normal npm package has been installed from the registry. You can then go ahead to include the code in OD and try it out.