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

@samhammer/ssp-ckeditor5-build-inline

v29.1.7

Published

The inline editor build of CKEditor 5 – the best browser-based rich text editor.

Downloads

54

Readme

CKEditor 5 inline editor build

Custom inline editor build for CKEditor 5 with additional Plugins from Samhammer AG.

Quick start

While development you can link plugins by its source code instead of package. This is done with lerna. (https://github.com/lerna/lerna)

Setp 1

Just create a folder "packages" in the root of this project and checkout your plugin to this folder

See also: lerna.json

Step 2

After checkout the project has to be initialized once before building it.

Ensure that you have a global installation of lerna 2.x.

Just run the following command to initialize the project and make it linkable (see further information below):

npm run bootstrap

Step 3

Run one of the following commands to create a production (minified) or dev version

npm run build
npm run builddev

How to use

This build can be referenced in other yarn based projects while development. This is done with the yarn link feature.

See also: https://yarnpkg.com/lang/en/docs/cli/link/

Yarn link is directly executed by the "yarn bootstrap" command. After this the development version of the package is provided for linking.

Execute the following command in your target project to use the dev version of the inline build:

yarn link @samhammer/ssp-ckeditor5-build-inline

Include in your JavaScript application:

import InlineEditor from '@samhammer/ckeditor5-build-inline';

InlineEditor
	.create(document.querySelector('#editor'))
	.then(editor => {
		window.editor = editor;
	})
	.catch(err => {
		console.error(err.stack);
	});

How to publish

For publishing an npm account that is referenced to the organization is required.

See the following how to:

https://yarnpkg.com/en/docs/publishing-a-package

If everything is configured correctly just count up the version number in our package.json and execute the following command:

npm publish

License

Licensed under the terms of GNU General Public License Version 2 or later. For full details about the license, please check the LICENSE.md file.