Bump Tiptap peerDependency packages to minimum of beta.210 with tiptap/pm package #47
+1,908
−961
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When switching any tiptap package to the beta.210+, we have to use
@tiptap/pm
for all prosemirror stuff exclusively, in order to ensure we have consistent prosemirror package versioning, as described in https://tiptap.dev/blog/new-pm-package-and-upgrade-guide-for-beta-210And as such this bumps all tiptap packages in peer dependencies to beta.210+, most notably to get around quirks with the prosemirror-tables extension as described in #45
This should allow mui-tiptap to be used with the latest verison of Tiptap. From some smoke-testing locally,
mui-tiptap
does appear to work on both beta.210 and on 2.0.3 (the latest official release).