The following guide describes how to integrate Tiptap with version 3 of Alpine.js.

For the sake of this guide we’ll use Vite to quickly set up a project, but you can use whatever you’re used to. Vite is just really fast and we love it.


1. Create a project (optional)

If you already have an existing Alpine.js project, that’s fine too. Just skip this step and proceed with the next step.

For the sake of this guide, let’s start with a fresh Vite project called my-tiptap-project. Vite sets up everything we need, just select the Vanilla JavaScript template.

npm init vite@latest my-tiptap-project -- --template vanilla
cd my-tiptap-project
npm install
npm run dev

2. Install the dependencies

Okay, enough of the boring boilerplate work. Let’s finally install Tiptap! For the following example you’ll need alpinejs, the @tiptap/core package, the @tiptap/pm package and the @tiptap/starter-kit, which includes the most common extensions to get started quickly.

npm install alpinejs @tiptap/core @tiptap/pm @tiptap/starter-kit

If you followed step 1, you can now start your project with npm run dev, and open http://localhost:5173 in your favorite browser. This might be different, if you’re working with an existing project.

3. Initialize the editor

To actually start using Tiptap, you’ll need to write a little bit of JavaScript. Let’s put the following example code in a file called main.js.

This is the fastest way to get Tiptap up and running with Alpine.js. It will give you a very basic version of Tiptap. No worries, you will be able to add more functionality soon.

import Alpine from 'alpinejs'
import { Editor } from '@tiptap/core'
import StarterKit from '@tiptap/starter-kit'

document.addEventListener('alpine:init', () => {'editor', (content) => {
    let editor // Alpine's reactive engine automatically wraps component properties in proxy objects. Attempting to use a proxied editor instance to apply a transaction will cause a "Range Error: Applying a mismatched transaction", so be sure to unwrap it using Alpine.raw(), or simply avoid storing your editor as a component property, as shown in this example.

    return {
      updatedAt:, // force Alpine to rerender on selection change
      init() {
        const _this = this

        editor = new Editor({
          element: this.$refs.element,
          extensions: [
          content: content,
          onCreate({ editor }) {
            _this.updatedAt =
          onUpdate({ editor }) {
            _this.updatedAt =
          onSelectionUpdate({ editor }) {
            _this.updatedAt =
      isLoaded() {
        return editor
      isActive(type, opts = {}) {
        return editor.isActive(type, opts)
      toggleHeading(opts) {
      toggleBold() {
      toggleItalic() {

window.Alpine = Alpine

4. Add it to your app

Now, let’s replace the content of the index.html with the following example code to use the editor in our app.

<!DOCTYPE html>
<html lang="en">
  <meta charset="UTF-8">
  <div x-data="editor('<p>Hello world! :-)</p>')">

    <template x-if="isLoaded()">
      <div class="menu">
          @click="toggleHeading({ level: 1 })"
          :class="{ 'is-active': isActive('heading', { level: 1 }, updatedAt) }"
          :class="{ 'is-active' : isActive('bold', updatedAt) }"
          :class="{ 'is-active' : isActive('italic', updatedAt) }"

    <div x-ref="element"></div>

  <script type="module" src="/main.js"></script>

    body { margin: 2rem; font-family: sans-serif; } { background: black; color: white; }
    .tiptap { padding: 0.5rem 1rem; margin: 1rem 0; border: 1px solid #ccc; }

You should now see Tiptap in your browser. Time to give yourself a pat on the back! :)