@tiptap-pro/extension-export-docx@1.0.0 has overly strict peer dependency on @tiptap/core

[magarrent]

Affected Packages

extension-export-docx

Version(s)

3.0.1

Description of the Bug

The stable 1.0.0 release of @tiptap-pro/extension-export-docx pins @tiptap/core to an exact version "3.0.1" in its peerDependencies, instead of using a semver range.

This causes ERESOLVE failures when used alongside any other @tiptap/core version (e.g. 3.15.1, 3.20.1):

npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: undefined@undefined
npm error Found: @tiptap/core@3.20.1
npm error
npm error Could not resolve dependency:
npm error peer @tiptap/core@"3.0.1" from @tiptap-pro/extension-export-docx@1.0.0

Expected behavior

The peer dependency should use a range like "^3.0.1", consistent with the beta releases. For example, 1.0.0-beta.9 correctly declares @tiptap/core: "^3.0.7" and works fine.

Comparison

Version	@tiptap/core peer dep
1.0.0-beta.9	^3.0.7 (range — works)
1.0.0 (stable)	3.0.1 (exact — breaks)

Workaround

Pin to the beta release:

"@tiptap-pro/extension-export-docx": "1.0.0-beta.9"
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: undefined@undefined
npm error Found: @tiptap/core@3.20.1
npm error
npm error Could not resolve dependency:
npm error peer @tiptap/core@"3.0.1" from @tiptap-pro/extension-export-docx@1.0.0