Plugins
React-based plugins are using Lexical editor instance from <LexicalComposer>
context:
<LexicalComposer initialConfig={initialConfig}>
<PlainTextPlugin
contentEditable={<ContentEditable />}
placeholder={<div>Enter some text...</div>}
/>
<HistoryPlugin />
<OnChangePlugin onChange={onChange} />
...
</LexicalComposer>
LexicalPlainTextPlugin
React wrapper for @lexical/plain-text
that adds major features for plain text editing, including typing, deletion and copy/pasting
<PlainTextPlugin
contentEditable={<ContentEditable />}
placeholder={<div>Enter some text...</div>}
/>
LexicalRichTextPlugin
React wrapper for @lexical/rich-text
that adds major features for rich text editing, including typing, deletion, copy/pasting, indent/outdent and bold/italic/underline/strikethrough text formatting
<RichTextPlugin
contentEditable={<ContentEditable />}
placeholder={<div>Enter some text...</div>}
/>
LexicalOnChangePlugin
Plugin that calls onChange
whenever Lexical state is updated. Using ignoreInitialChange
(true
by default) and ignoreSelectionChange
(false
by default) can give more granular control over changes that are causing onChange
call
<OnChangePlugin onChange={onChange} />
LexicalHistoryPlugin
React wrapper for @lexical/history
that adds support for history stack management and undo
/ redo
commands
<HistoryPlugin />
LexicalLinkPlugin
React wrapper for @lexical/link
that adds support for links, including toggleLink
command support that toggles link for selected text
<LinkPlugin />
LexicalListPlugin
React wrapper for @lexical/list
that adds support for lists (ordered and unordered)
<ListPlugin />
LexicalCheckListPlugin
React wrapper for @lexical/list
that adds support for check lists. Note that it requires some css to render check/uncheck marks. See PlaygroundEditorTheme.css for details.
<CheckListPlugin />
LexicalTablePlugin
React wrapper for @lexical/table
that adds support for tables
<TablePlugin />
LexicalAutoLinkPlugin
Plugin will convert text into links based on passed matchers list. In example below whenever user types url-like string it will automaticaly convert it into a link node
const URL_MATCHER =
/((https?:\/\/(www\.)?)|(www\.))[-a-zA-Z0-9@:%._+~#=]{1,256}\.[a-zA-Z0-9()]{1,6}\b([-a-zA-Z0-9()@:%_+.~#?&//=]*)/;
const MATCHERS = [
(text) => {
const match = URL_MATCHER.exec(text);
return (
match && {
index: match.index,
length: match[0].length,
text: match[0],
url: match[0],
}
);
},
];
...
<AutoLinkPlugin matchers=[MATCHERS] />
LexicalAutoScrollPlugin
Lexical auto-scrolls its contenteditable container while typing. This plugin can be used for cases when other element up in a DOM tree needs to be scrolled (e.g. when editor is rendered within dialog with limited height):
<div ref={containerWithScrollRef}>
<LexicalComposer>
...
<AutoScrollPlugin scrollRef={containerWithScrollRef} />
</LexicalComposer>
</div>
LexicalClearEditorPlugin
Adds clearEditor
command support to clear editor's content
LexicalMarkdownShortcutPlugin
Adds markdown shortcut support: headings, lists, code blocks, quotes, links and inline styles (bold, italic, strikethrough)
TableOfContentsPlugin
This plugin allows you to navigate to certain sections of the page by clicking on headings that exist inside these sections. Once you load the plugin, it automatically collects and injects the headings of the page inside the table of contents, then it listens to any deletions or modifications to those headings and updates the table of contents. Additionally, it's able to track any newly added headings and inserts them in the table of contents once they are created. This plugin also supports lazy loading - so you can defer adding the plugin until when the user needs it.
<TableOfContentsPlugin />
You can alternatively leverage the use of LexicalTableOfContents__EXPERIMENTAL
API, which provides you with all the functioanlity that TableOfContentsPlugin
provides, but without any styling.
In order to use LexicalTableOfContents__EXPERIMENTAL
, you need to pass a callback function in its children. This callback function gives you access to the up-to-date data of the table of contents. You can access this data through a single parameter for the callback which comes in the form of an array of arrays [[headingKey, headingTextContent, headingTag], [], [], ...]
headingKey
: Unique key that identifies the heading.headingTextContent
: A string of the exact text of the heading.headingTag
: A string that reads either 'h1', 'h2', or 'h3'.
<LexicalTableOfContents__EXPERIMENTAL>
{(tableOfContentsArray) => {
return <MyCustomTableOfContetsPlugin tableOfContents={tableOfContentsArray} />;
}}
</LexicalTableOfContents__EXPERIMENTAL>