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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@knime/kds-rich-text-editor

v2.6.0

Published

Package containing the RichTextEditor component which follows the KNIME Design System

Readme

KNIME® Design System – Rich Text Editor

This is part of the KNIME Design System.

This package contains the KdsRichTextEditor component and its toolbar, a WYSIWYG editor that follows the KNIME Design System. It is based on the Vue JavaScript framework, built on the KNIME Design System tokens, and powered by Tiptap/ProseMirror.

It's published as npm package: @knime/kds-rich-text-editor

Why a separate package?

Tiptap and ProseMirror add a large, DOM-parsing dependency subtree (~50 packages) that is irrelevant to most consumers of @knime/kds-components. Keeping the editor in its own package keeps that dependency, bundle, and security-audit/SBOM surface opt-in — only apps that install this package pull it in. See the root README for the package overview.

The Tiptap/ProseMirror packages are declared as regular dependencies but are externalized in the build (see vite.config.js). They are resolved at consume time rather than bundled, so consumers dedupe a single ProseMirror instance and can pull CVE-patched transitive versions via their own lockfile without waiting on a republish.

Development

This package is part of the KNIME Design System monorepo. For setup instructions, see the root README.

Launch development server

From the root of the monorepo:

pnpm dev       # Starts Storybook with all design system components

Testing

Unit tests are based on Vitest. Run from the monorepo root:

pnpm run test:unit      # Run all unit tests (packages/*)
pnpm run coverage       # Generate coverage reports

Running security audit

Security audits are run at the monorepo root:

pnpm run audit

Logging

You can log using the global consola variable (which the embedding application needs to provide).

See https://github.com/nuxt/consola for details.

Building

To build the editor as a Vue library:

pnpm run build      # Build only this package

Results are saved to dist/.

Versioning & Publishing

Versioning and publishing are managed at the root level.

All @knime/kds-* packages (including this one) are versioned together via Changesets. For release workflows, see the root README.

Using the editor in a Vue application

Install the @knime/kds-rich-text-editor npm package as a dependency. It requires @knime/kds-components and vue as peer dependencies:

pnpm add @knime/kds-rich-text-editor @knime/kds-components @knime/kds-styles
<script setup lang="ts">
import { ref } from "vue";

import { KdsRichTextEditor } from "@knime/kds-rich-text-editor";

const value = ref("<p>Hello world</p>");
</script>

<template>
  <KdsRichTextEditor
    v-model="value"
    :base-extensions="{ bold: true, italic: true, link: true }"
  />
</template>

Public exports

All public symbols follow the KDS Kds prefix convention:

| Export | Kind | Description | | --------------------------- | --------- | --------------------------------------------------- | | KdsRichTextEditor | component | The editor (with built-in toolbar) | | KdsCreateLinkModal | component | Modal used by the link tool | | kdsDefaultLinkToolOptions | const | Default URL validator / sanitizer for the link tool | | KdsLinkToolOptions | type | Options for the link tool | | KdsRichTextEditorProps | type | Props of KdsRichTextEditor | | KdsBaseExtensionsConfig | type | Opt-in map of built-in Tiptap extensions |

Using with Vitest, Nuxt, or Vite SSR

The published JavaScript imports its CSS as a side effect (e.g. import "./index.css"), which bundlers handle automatically. When the package is instead evaluated by Node's native ESM loader — as Vitest and Vite/Nuxt SSR do by default, since they externalize node_modules — Node has no .css loader and throws Unknown file extension ".css". Configure the consuming project once so @knime/* packages are processed instead of externalized:

// Vitest — vitest.config.ts
export default defineConfig({
  test: { server: { deps: { inline: [/@knime\//] } } },
});
// Vite SSR — vite.config.ts
export default defineConfig({ ssr: { noExternal: [/@knime\//] } });
// Nuxt — nuxt.config.ts
export default defineNuxtConfig({ build: { transpile: [/@knime\//] } });

Requirements

The editor expects that the embedding app provides the following:

  • Vue and Consola compatible to the versions defined in package.json
  • @knime/kds-components and the @knime/kds-styles CSS variables imported once in the app entry