Skip to main content


Thanks for your interest in improving slate-plugins! We are a community-driven project and welcome contributions of all kinds: from discussion to documentation to bugfixes to feature improvements.

Please review this document to help to streamline the process and save everyone's precious time.


No software is bug-free. So, if you got an issue, follow these steps:

  • Search the issue list for current and old issues.
    • If you find an existing issue, please UPVOTE the issue by adding a "thumbs-up reaction". We use this to help prioritize issues!
  • If none of that is helping, create an issue with the following information:
    • Clear title (shorter is better).
    • Describe the issue in clear language.
    • Share error logs, screenshots, etc.
    • To speed up the issue fixing process, send us the steps to reproduce or a sample repo with the issue you faced:


The best way to help figure out an issue you are having is to produce a minimal reproduction using our CodeSandbox

Development Guide#

Initial Setup#

This repo uses yarn workspaces, so you should install yarn as the package manager. See installation guide.

  1. cd ~ (optional)
  2. git clone bonus: use your own fork for this step
  3. cd slate-plugins
  4. yarn


  1. cd docs
  2. yarn
  3. yarn start


Run Linter#

We use eslint as a linter for all code (including typescript code).

All you have to run is:

yarn lint --fix

Run unit tests#

This command will list all the suites and options for running tests.

yarn test

The options for running tests can be selected from the cli or be passed to yarn test with specific parameters. Available modes include --watch, --coverage, and --runInBand, which will respectively run tests in watch mode, output code coverage, and run selected test suites serially in the current process.

Updating Tests#

Before any contributions are submitted in a PR, make sure to add or update meaningful tests. A PR that has failing tests will be regarded as a “Work in Progress” and will not be merged until all tests pass. When creating new unit test files, the tests should adhere to a particular folder structure and naming convention, as defined below.

# Proper naming convention and structure for test files
+-- filename_to_test.spec.ts

When using slate-hyperscript, include this at the top of the file:

/** @jsx jsx */
import { jsx } from "@udecode/slate-plugins-test-utils";

Example of input and output being an editor containing one paragraph:

const input = ((
) as any) as Editor;
const output = ((
) as any) as Editor;
it("should be", () => {

Release Guide#

This section is for anyone wanting a release. The current release sequence is as follows:

  • Commit your changes:
    • If you want to synchronize the exports, run yarn cti to automatically update the index files.
    • Lint, test, build should pass.
  • Open a PR against main and add a changeset.
  • To create a snapshot release, maintainers can comment a GitHub issue starting with /release:next.
  • Merge the PR, triggering the bot to create a PR release.
  • Review the final changesets.
  • Merge the PR release, triggering the bot to release the changed packages on npm.

Pull Requests (PRs)#

We welcome all contributions. There are many ways you can help us. This is few of those ways:

Before you submit a new PR, make sure you run yarn test. Do not submit a PR if tests are failing. If you need any help, the best way is to join slate's Slack and ask in the slate-plugins channel.

Reviewing PRs#

As a PR submitter, you should reference the issue if there is one, include a short description of what you contributed and, if it is a code change, instructions for how to manually test out the change. This is informally enforced by our PR template. If your PR is reviewed as only needing trivial changes (e.g. small typos etc), and you have commit access then you can merge the PR after making those changes.

As a PR reviewer, you should read through the changes and comment on any potential problems. If you see something cool, a kind word never hurts either! Additionally, you should follow the testing instructions and manually test the changes. If the instructions are missing, unclear, or overly complex, feel free to request better instructions from the submitter. Unless the PR is a draft, if you approve the review and there is no other required discussion or changes, you should also go ahead and merge the PR.

Issue Triage#

If you are looking for a way to help the project, triaging issues is a great place to start. Here's how you can help:

Responding to questions#

Q&A is a great place to help. If you can answer a question, it will help the asker as well as anyone who has a similar question. Also in the future if anyone has that same question they can easily find it by searching. If an issue needs reproduction, you may be able to guide the reporter toward one, or even reproduce it yourself using this technique.

Triaging issues#

Once you've helped out on a few issues, if you'd like triage access you can help label issues and respond to reporters.

We use the following label scheme to categorize issues:

  • type - bug, feature, dependencies, maintenance.
  • area - plugin:x, plugin:list, plugin:common, ui, etc.
  • status - needs reproduction, etc.

All issues should have a type label. dependencies is for keeping package dependencies up to date. maintenance is a catch-all for any kind of cleanup or refactoring.

They should also have one or more area/status labels. We use these labels to filter issues down so we can see all of the issues for a particular area, and keep the total number of open issues under control.

For example, here is the list of open, untyped issues. For more info see searching issues in the Github docs.

If an issue is a bug, and it doesn't have a clear reproduction that you have personally confirmed, label it needs reproduction and ask the author to try and create a reproduction, or have a go yourself.

Closing issues#

  • Duplicate issues should be closed with a link to the original.
  • Unreproducible issues should be closed if it's not possible to reproduce them (if the reporter drops offline, it is reasonable to wait 2 weeks before closing).
  • bugs should be closed when the issue is fixed and released.
  • features, maintenances, should be closed when released or if the feature is deemed not appropriate.