[Bug]: Invalid regular expression: invalid group specifier name (introduced in 2.10.3)

[erwamartin]

Affected Packages

extension-code

Version(s)

2.10.3

Bug Description

The TipTap code extension fails to load on Safari versions below 16 due to the following error:

Invalid regular expression: invalid group specifier name.

This issue prevents the file from being loaded and stems from an incompatible regex introduced in this commit:
ueberdosis/tiptap commit f79c05e.

The regex uses named capturing groups and lookbehind assertions, which are not supported in Safari versions earlier than 16.

Browser Used

Safari

Code Example URL

No response

Expected Behavior

The file should load correctly.

Rewritten Regex
Original:

export const inputRegex = /(?<!`)`([^`]+)`(?!`)/;
export const pasteRegex = /(?<!`)`([^`]+)`(?!`)/g;

Rewritten Without Lookbehind:

export const inputRegex = /(^|[^`])`([^`]+)`(?!`)/;
export const pasteRegex = /(^|[^`])`([^`]+)`(?!`)/g;

Additional Context (Optional)

No response

Dependency Updates

• Yes, I've updated all my dependencies.

[wallisonfelipe]

Same here:
Invalid regular expression: invalid group specifier name

[nperez0111]

Would happily accept a PR to address this

[lino-levan]

This issue was fixed in #5916. I guess we're waiting on that to be released.

[nperez0111]

Yes, we queue releases. If you need it now, you can use the PR's version: #5916 (comment)

[lino-levan]

Any timeline on when the next version of tiptap will be released?

[nperez0111]

No, we release when we feel ready. Please refer to my previous comment above

If you need it now, you can use the PR's version

[ccreusat]

Hi guys !

For your information, we have the same problem with Tiptap and the code extension in version 2.3.0 in Safari 15.6 and below (but that's ok I think). Works in Safari 16.5, 17.6, ... 👍🏼

[Nantris]

Whoops I see I've duplicated this issue in #5948.

I've closed it as a duplicated, but I've suggested a more robust approach there that brings the best of both worlds.

[Nantris]

I think this was already released though and issues persist? So now I'm not sure I've really duplicated the issue. Anyway, sorry, that's enough cluttering your inboxes. Looking forward to a resolution.