Cms: Multiple versions of Prosemirror-model loaded

[mikemartin]

Bug Description

When editing a Bard field inside a Bard set, you get the following error when creating a new line:
Uncaught RangeError: Can not convert <> to a Fragment (looks like multiple versions of prosemirror-model were loaded).

This is possibly related to https://github.com/ueberdosis/tiptap/issues/577 or the latest Statamic update: https://github.com/statamic/cms/commit/b74c61e05

Extra Detail

Environment

Statamic 3.0.31 Pro
Laravel 8.16.1
PHP 7.4.9
statamic/migrator dev-master
statamic/seo-pro 2.0.14

Install method (choose one):

• Fresh install from statamic/statamic

[robdekort]

Was able to reproduce this in Firefox. In Safari it seems to work.

[robdekort]

I took the liberty to label this critical.

[felixstoessel]

Same issue here using Firefox. If I am at the end of a paragraph/line in Bard and try to enter <return>, I get this issue.

[adnankussair]

Yup same issue here. Certain bard formatting options are throwing the prose mirror console error the one we experiencing it on was blockquote.

[ellukesmith]

I'm getting the same error in Chrome, but I don't have a Bard field inside a Bard set - adding a Bard field with default options to any Blueprint has the same issue. I'm also getting the same error in Safari - every time I hit enter, it throws the same error in the console.

Running the same version of Statamic (3.0.31 Pro).

UPDATE: Rolling back to 3.0.30 Pro stopped the issue for me. I agree with @mikemartin on this one, it was likely the upgrade of tiptap-extensions that's causing the issue.

[jeremydouglas]

I get this error on 3.0.31 when there's multiple Bards on a collection entry. Both in Chrome and Firefox.

[jasonvarga]

Tackling this shortly.

[adnankussair]

Tackling this shortly.

Whoot! Thanks @jasonvarga