v3.18.0

[bdbch]

@tiptap/extension-bubble-menu

Patch Changes

• Fix BubbleMenu and FloatingMenu props not updating after initialization

@tiptap/extension-floating-menu

Patch Changes

• Fix BubbleMenu and FloatingMenu props not updating after initialization

@tiptap/react

Minor Changes

• Introduce a new, optional React integration that provides a declarative <Tiptap /> component for setting up editors in React apps.

  Summary

  • Add a new, ergonomic way to initialize and use Tiptap editors in React via <Tiptap /> components. This is an additive change and does not remove or change existing APIs.

  Why this change

  • Improves ergonomics for React users by offering a component-first API that pairs well with React patterns (hooks, JSX composition and props-driven configuration).

  Migration and usage

  • The old programmatic setup remains supported for this major version — nothing breaks. We encourage consumers to try the new <Tiptap /> component and migrate when convenient.

  Example

  import { Tiptap, useEditor } from '@tiptap/react'
  
  function MyEditor() {
    const editor = useEditor({ extensions: [StarterKit], content: '<h1>Hello from Tiptap</h1>' })
  
    return (
      <Tiptap instance={editor}>
        <Tiptap.Content />
        <Tiptap.BubbleMenu>My Bubble Menu</Tiptap.BubbleMenu>
        <Tiptap.FloatingMenu>My Floating Menu</Tiptap.FloatingMenu>
        <MenuBar /> {/* MenuBar can use the new `useTiptap` hook to read the editor instance from context */}
      </Tiptap>
    )
  }

  Deprecation plan

  • The old imperative setup will remain fully backward-compatible for this major release. We plan to deprecate (and remove) the legacy setup in the next major version — a deprecation notice and migration guide will be published ahead of that change.

Patch Changes

• Fix BubbleMenu and FloatingMenu props not updating after initialization
• Fixed extension storage not updating in React and Vue node views

@tiptap/vue-3

Patch Changes

• Fixed extension storage not updating in React and Vue node views

@tiptap/markdown

Patch Changes

• Upgrade marked.js from v15.0.12 to v17.0.1. Note that **)** requires whitespace when adjacent to alphanumeric text per CommonMark specification.

@tiptap/extensions

Patch Changes

• Added a new dataAttribute to the extension option to control which attribute name will be used for the placeholder label.

---

This discussion was created from the release v3.18.0.

[mattkrick]

Upgrading markedjs to v16+ has breaking changes & will break jest tests. Can I suggest:

• Upgrade the change from Patch to Breaking (even if it's just by name in the changelog & not semver, I understand keeping the versions pinned at 3.x is desired)
• Add a line including how to migrate jest.config:
  • transformIgnorePatterns: ['/node_modules/(?!(marked)/)'] | transformIgnorePatterns: ['/marked\.esm\.js/'],
• Add a link to the breaking changes upstream: https://github.com/markedjs/marked/releases/tag/v16.0.0

[bdbch]

Thanks for reporting. I wasn't aware of Jest breaking on our end so couldn't see this before. Since this was just a maintenance bump, we could revert it and do the bump with v4?

[mattkrick]

I'll take a failing jest test in CI/CD over a broken list item that was fixed in marked v16.
IMO it's better to be on latest with all the fixes than be 100% semantically correct in versioning, especially since it's just tooling.