Error: LinkPlugin: LinkNode not registered on editor

[blackrabbit944]

i am tring to use the Lexical in my project , just trying to make a demo, but it has an error i don't know why:

import {$getRoot, $getSelection} from 'lexical';
import {useEffect} from 'react';

import {LexicalComposer} from '@lexical/react/LexicalComposer';
import {RichTextPlugin} from '@lexical/react/LexicalRichTextPlugin';
import {ContentEditable} from '@lexical/react/LexicalContentEditable';
import {HistoryPlugin} from '@lexical/react/LexicalHistoryPlugin';
import {LinkPlugin} from '@lexical/react/LexicalLinkPlugin';
import {OnChangePlugin} from '@lexical/react/LexicalOnChangePlugin';
import {useLexicalComposerContext} from '@lexical/react/LexicalComposerContext';

const theme = {
  // Theme styling goes here
}

// When the editor changes, you can get notified via the
// LexicalOnChangePlugin!
function onChange(editorState) {
  editorState.read(() => {
    // Read the contents of the EditorState here.
    const root = $getRoot();
    const selection = $getSelection();

    console.log(root, selection);
  });
}

// Lexical React plugins are React components, which makes them
// highly composable. Furthermore, you can lazy load plugins if
// desired, so you don't pay the cost for plugins until you
// actually use them.
function MyCustomAutoFocusPlugin() {
  const [editor] = useLexicalComposerContext();

  useEffect(() => {
    // Focus the editor when the effect fires!
    editor.focus();
  }, [editor]);

  return null;
}

// Catch any errors that occur during Lexical updates and log them
// or throw them as needed. If you don't throw them, Lexical will
// try to recover gracefully without losing user data.
function onError(error) {
  console.error(error);
}

export default function Editor() {
  const initialConfig = {
    namespace: 'sosponge-editor', 
    theme,
    onError,
  };

  return (
    <div className='prose relative mx-auto p-8'>
    <LexicalComposer initialConfig={initialConfig}>
      <RichTextPlugin
        contentEditable={<ContentEditable />}
        placeholder={<div className='absolute left-8 top-8 pointer-events-none'>
            <p className='text-gray-400'>Enter text...</p>
        </div>}
      />
      <OnChangePlugin onChange={onChange} />
      <HistoryPlugin />
      <LinkPlugin />
      <MyCustomAutoFocusPlugin />
    </LexicalComposer>
    </div>
  );
}

Unhandled Runtime Error
Error: LinkPlugin: LinkNode not registered on editor

is there any thing i missed ?
thanks

[blackrabbit944]

finally i found in Playground Example

import nodes from './nodes/nodes.js'

const initialConfig = {
    namespace: 'sosponge-editor', 
    theme,
    onError,
    nodes : [...nodes]
  };

[afreeland]

I guess I am still missing and unsure how to register the <LinkPlugin /> or why it is treated differently than

<OnChangePlugin onChange={onChange} />
<HistoryPlugin />
<MyCustomAutoFocusPlugin />

Received the same error above for LinkPlugin and for LexicalAutoLinkPlugin when trying to experiment with Lexical.

[afreeland]

I think I see from the demo that there is an AutoLinkNode that does get utilized. Still not sure why the others are naturally able to be used...probably need to read up on nodes and plugins.

I was able to import { AutoLinkNode } from '@lexical/link'; and then registered nodes: [AutoLinkNode] in the initialConfig and things started working as desired.

[Aaasisss]

this worked for me.
you can import different node similarly.

import { AutoLinkNode, LinkNode } from "@lexical/link";
import { ListNode, ListItemNode } from "@lexical/list";
import { TableNode, TableCellNode, TableRowNode } from "@lexical/table";

and then pass them into the nodes array in the editorConfigs object

  const editorConfig = {
      namespace: "React.js Demo",
      nodes: [
        LinkNode,
        AutoLinkNode,
        ListNode,
        ListItemNode,
        TableNode,
        TableCellNode,
        TableRowNode,
      ],
      onError(error: Error) {
        throw error;
      },
      theme: theme,
    };

[echarles]

BTW see question posted on #2739

Why do are the node registrations decoupled from the plugins?