You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Last version released (2.0.0-beta.126) broke compatibilty with my company custom extensions, that were running good with previous relese (2.0.0-beta.113). We've just noticed that after an npm install.
Following the fresh error
I don't even know what that means, and 'm not going to investigate this, all I know is that the first time this incident happened I've had to rewrite our custom extensions.
You cannot sponsor tiptap as
Create exactly the rich text editor you want out of customizable building blocks. Tiptap comes with sensible defaults, a lot of extensions and a friendly API to customize every aspect.
if you keep broke the sistem behind custom extensions, can you?
We had to rollback to version 2.0.0-beta.113.
Thanks
How can we reproduce the bug on our side?
-Install version 2.0.0-beta.113
-Write your own custom extension with old sintax
-run npm install
-tiptap core update to 2.0.0-beta.126
-everithing broken now
Can you provide a CodeSandbox?
No response
What did you expect to happen?
That everything works in a consistent way from version to version
Anything to add? (optional)
No response
Did you update your dependencies?
Yes, I’ve updated my dependencies to use the latest version of all packages.
Are you sponsoring us?
Yes, I’m a sponsor. 💖
The text was updated successfully, but these errors were encountered:
@philippkuehn maybe you need to keep a changelog, won't be super useful? PR and github issue is not a replacement for a well written changelog, especially for breaking changes.
Today, 27/10/2021 the page https://tiptap.dev/changelog is still empty, that's a shame.
That possibly avoid future issues like mine, and looking at PR 1997, many others.
What’s the bug you are facing?
Last version released (2.0.0-beta.126) broke compatibilty with my company custom extensions, that were running good with previous relese (2.0.0-beta.113). We've just noticed that after an npm install.
Following the fresh error

I don't even know what that means, and 'm not going to investigate this, all I know is that the first time this incident happened I've had to rewrite our custom extensions.
You cannot sponsor tiptap as
if you keep broke the sistem behind custom extensions, can you?
We had to rollback to version 2.0.0-beta.113.
Thanks
How can we reproduce the bug on our side?
-Install version 2.0.0-beta.113
-Write your own custom extension with old sintax
-run npm install
-tiptap core update to 2.0.0-beta.126
-everithing broken now
Can you provide a CodeSandbox?
No response
What did you expect to happen?
That everything works in a consistent way from version to version
Anything to add? (optional)
No response
Did you update your dependencies?
Are you sponsoring us?
The text was updated successfully, but these errors were encountered: