Skip to content

Payload Editor

Payload Lexical configuration

@nexload-sdk/payload-editor

v1.1.0 Stable Released

Semantic, deterministic Payload Lexical editor configuration.

Payload CMSNode.jsESM

@nexload-sdk/payload-editor 1.1.0 turns an explicit semantic feature definition into the official Payload Lexical editor provider. It gives teams named presets, deterministic merge rules, validation, and a safe extension seam without owning editor UI.

Use it when multiple collections need a reviewable editor policy. Use lexicalEditor directly when each collection needs unrelated native configuration.

The package runs in server/config code and is ESM-only. It has no React, CSS, browser-global, theme, AI-provider, or Admin component runtime. Actual editing behavior and persistence remain owned by @payloadcms/richtext-lexical.

It does not define Payload fields. Assign the returned provider to a rich-text field or Payload’s root editor option.

  1. Install matched Payload peers.
  2. Build an explicit editor in the quick start.
  3. Learn feature state, preset, merge, and extension concepts.
  4. Apply task-focused guides.
  5. Use the API and troubleshooting pages as references.

These pages document the current package version; historical documentation is not hosted.