Uncaught RangeError: Adding different instances of a keyed plugin (plugin$)

[avitorio]

Discussed in #75

^{Originally posted by mtaku3 November 25, 2022}
Hi, I'm planning to adapt outstatic on my own portfolio project.
When I tried your example/blog application, I got RangeError: Adding different instances of a keyed plugin (plugin$) on new content page(/outstatic/projects/new, /outstatic/posts/new and /outstatic/pages/new)
Do you have any solution for this?

Code I have tried

https://github.com/avitorio/outstatic/tree/canary/examples/blog

Environment

node v18.11.0
npm 8.19.2

Whole of the error message

Uncaught RangeError: Adding different instances of a keyed plugin (plugin$)
    at eval (index.js?fff7:726:1)
    at Array.forEach (<anonymous>)
    at new Configuration (index.js?fff7:724:1)
    at EditorState.reconfigure (index.js?fff7:861:1)
    at Editor.createView (tiptap-core.esm.js?ab32:3471:1)
    at new Editor (tiptap-core.esm.js?ab32:3306:1)
    at new Editor (tiptap-react.mjs?05ef:34:1)
    at eval (tiptap-react.mjs?05ef:347:1)
    at commitHookEffectListMount (react-dom.development.js?ac89:23150:1)
    at commitPassiveMountOnFiber (react-dom.development.js?ac89:24926:1)
    at commitPassiveMountEffects_complete (react-dom.development.js?ac89:24891:1)
    at commitPassiveMountEffects_begin (react-dom.development.js?ac89:24878:1)
    at commitPassiveMountEffects (react-dom.development.js?ac89:24866:1)
    at flushPassiveEffectsImpl (react-dom.development.js?ac89:27039:1)
    at flushPassiveEffects (react-dom.development.js?ac89:26984:1)
    at performSyncWorkOnRoot (react-dom.development.js?ac89:26076:1)
    at flushSyncCallbacks (react-dom.development.js?ac89:12042:1)
    at commitRootImpl (react-dom.development.js?ac89:26959:1)
    at commitRoot (react-dom.development.js?ac89:26682:1)
    at finishConcurrentRender (react-dom.development.js?ac89:25981:1)
    at performConcurrentWorkOnRoot (react-dom.development.js?ac89:25809:1)
    at workLoop (scheduler.development.js?bcd2:266:1)
    at flushWork (scheduler.development.js?bcd2:239:1)
    at MessagePort.performWorkUntilDeadline (scheduler.development.js?bcd2:533:1)

Additional Info:

This seems to have something to do with the TipTap's Placeholder extension, as removing it makes the page load correctly (but without the Placeholder)