Contribute to this guide

guideJavaScript package content

This guide describes the contents of the JavaScript package generated by the Package Generator.

# Structure of the project

An overview of the project’s directory structure:

├─ lang
│  └─ contexts.json        # Entries used for creating translations.
├─ sample
│  ├─ dll.html             # The editor initialized using the DLL builds.
│  ├─ index.html           # The sample file.
│  └─ ckeditor.js          # The editor initialization script.
├─ src
│  ├─ index.js             # The modules exported by the package when using the DLL builds.
│  ├─ myplugin.js          # Very basic plugin that utilizes the CKEditor 5 framework.
│  └─ **/*.js              # All JavaScript source files should be saved here.
├─ tests
│  ├─ index.js             # Tests for the plugin.
│  ├─ myplugin.js
│  └─ **/*.js              # All tests should be saved here.
├─ theme
│  ├─ icons
│  │  ├─ ckeditor.svg      # The CKEditor 5 icon displayed in the toolbar.
│  │  └─ **/*.svg          # All icon files should be saved here.
│  └─ **/*.css             # All CSS files should be saved here.
│
├─ .editorconfig           # See link below for details.
├─ .eslintrc.js            # ESLint configuration file.
├─ .gitattributes          # See link below for details.
├─ .gitignore              # See link below for details.
├─ .stylelintrc            # Stylelint configuration file.
├─ ckeditor5-metadata.json # See link below for details.
├─ LICENSE.md              # All created packages fall under the MIT license.
├─ package.json            # See link below for details.
└─ README.md               # Description of your project and usage instructions.

Guides for developing some of the files:

# Npm scripts

Npm scripts are a convenient way to provide commands in a project. They are defined in the package.json file and shared with other people contributing to the project. It ensures that the developers use the same commands with the same options (flags).

All the scripts can be executed by running npm run <script>. Pre and post commands with matching names will be run for those as well.

The following scripts are available in the package.

# start

Starts a HTTP server with the live-reload mechanism that allows previewing and testing plugins available in the package.

When the server has been started, the default browser will open the developer sample. This can be disabled by passing the --no-open option to that command.

You can also define the language that will translate the created editor by specifying the --language [LANG] option. It defaults to 'en'.

Examples:

# Starts the server and opens the browser.
npm run start

# Disable auto-opening the browser.
npm run start -- --no-open

# Create the editor with the interface in German.
npm run start -- --language=de

# test

Allows executing unit tests for the package, specified in the tests/ directory. The command accepts the following modifiers:

  • --coverage – to create the code coverage report.
  • --watch – to observe the source files (the command does not end after executing tests).
  • --source-map – to generate source maps of the sources.
  • --verbose – to print additional webpack logs.

Examples:

# Execute tests.
npm run test

# Generate code coverage report after each change in the sources.
npm run test -- --coverage --test

# lint

Runs ESLint, which analyzes the code (all *.js files) to quickly find problems.

Examples:

# Execute ESLint.
npm run lint

# stylelint

Similar to the lint task, stylelint analyzes the CSS code (*.css files in the theme/ directory) in the package.

Examples:

# Execute stylelint.
npm run stylelint

# dll:build

Creates a DLL-compatible package build which can be loaded into an editor using DLL builds.

Examples:

# Build the DLL file that is ready to publish.
npm run dll:build

# Build the DLL file and listen to changes in its sources.
npm run dll:build -- --watch

# dll:serve

Creates a simple HTTP server (without the live-reload mechanism) that allows verifying whether the DLL build of the package is compatible with the CKEditor 5 DLL builds.

Examples:

# Starts the HTTP server and opens the browser.
npm run dll:serve

You can run npm run dll:build -- --watch and npm run dll:serve in two separate command terminals. That way, after you save your changes and reload the page, the content will update.

# translations:collect

Collects translation messages (arguments of the t() function) and context files, then validates whether the provided values do not interfere with the values specified in the @ckeditor/ckeditor5-core package.

The task may end with an error if one of the following conditions is met:

  • Found the Unused context error – entries specified in the lang/contexts.json file are not used in source files. They should be removed.
  • Found the Context is duplicated for the id error – some of the entries are duplicated. Consider removing them from the lang/contexts.json file, or rewrite them.
  • Found the Context for the message id is missing error – entries specified in the source files are not described in the lang/contexts.json file. They should be added.

Examples:

npm run translations:collect

# translations:download

Download translations from the Transifex server. Depending on users’ activity in the project, it creates translations files used for building the editor.

The task requires passing an organization and project names. Usually, it matches the following format: https://www.transifex.com/[ORGANIZATION]/[PROJECT].

To avoid passing these options every time the command calls for it, you can store it in package.json, next to the ckeditor5-package-tools translations:download command.

Examples:

npm run translations:download -- --organization [ORGANIZATION] --project [PROJECT]

# translations:upload

Uploads translation messages onto the Transifex server. It allows for the creation of translations into other languages by users using the Transifex platform.

The task requires passing an organization and project names. Usually, it matches the following format: https://www.transifex.com/[ORGANIZATION]/[PROJECT].

To avoid passing these options every time the command calls for it, you can store it in package.json, next to the ckeditor5-package-tools translations:upload command.

Examples:

npm run translations:upload -- --organization [ORGANIZATION] --project [PROJECT]

# prepare

Npm supports some special life cycle scripts that allow automatically performing operations in certain situations:

  • prepare: Triggers during package creation and before publishing.

That script simply creates a DLL-compatible package build after creation and before publishing the package.

# How to change ESLint configuration?

To change the ESLint configuration, edit the .eslintrc.js file. It is also a good idea to check out the ESLint docs.

To make CKEditor 5 plugins compatible with each other, we needed to introduce certain limitations when importing files from packages. To learn more, visit the DLL guide and see a detailed explanation about the limitations.

# Translations

Packages created by this tool, just like the entirety of the CKEditor 5 ecosystem, include full support for localization. If you wish to include translations for your package, visit the dedicated translation guide and learn more.

The package generator provides several tools for handling translations in the created package. We recommend the following flow when dealing with translations:

  1. Call npm run translations:download – download the latest version of translations.
    • If there are changes in the lang/translations/* files, commit them as they represent new or updated translation files.
  2. Call npm run translations:collect – verify whether contexts are up-to-date.
  3. Call npm run translations:upload – upload new translations.
  4. Call npm run translations:download – if new contexts were uploaded, it updates the en.po file in the package. Do not forget to commit the change.

# Reporting issues

If you found a problem with CKEditor 5 or the package generator, please, report an issue: