Shreya Taneja, Project ManagerEddyter ships often — 84 versions are live on npm, and 1.4.24 went out eight days before this recording. This walkthrough is the whole upgrade path in 66 seconds: check what you're running, update, type-check, restart, confirm the editor still mounts. The project goes from Eddyter 1.4.23 to 1.4.24 with zero code changes.
The project is Eventide, a real Next.js event management web application with an admin console, events, blog, notes and team chat. Eddyter is already embedded in its note composer. Before the upgrade, the badge in the editor footer reads v1.4.23.
The upgrade runs inside Claude Code from a single instruction: "update eddyter to the latest version."
The installed version is compared against what npm serves. Result: installed 1.4.23, latest 1.4.24. Nothing else is touched until that comparison is made.
The dev server is stopped before the package is replaced. This matters more than it looks — Next.js holds the old module graph in memory, so upgrading under a live server gives you a stale editor and a confusing first render.
A type-check runs immediately after the update. Clean. On a patch release this is a five-second check that tells you whether any prop or export signature moved.
The server comes back up on localhost:3000, the Eventide homepage loads, the Notes composer is opened, and the Eddyter toolbar mounts with no license error. The footer badge now reads v1.4.24.
If you're not driving it through an agent, the upgrade is one command:
bash
Then restart your dev server and reload the page. Install reference: the eddyter package on npm.
Nothing in the integration. ConfigurableEditorWithAuth and EditorProvider stay exactly as they were, the API key stays the same, and no config file is edited. That is the point of a patch release — see the full integration reference in the Eddyter docs.
Your license key is bound to an origin, not to a package version, so an upgrade will not invalidate it — but a port change will. If your key is registered against localhost:3000, pin the dev server to that port instead of letting it auto-assign. You can confirm the registered origin on your license key page.
Second: know how to read your current version. The editor footer prints it next to "Report a Bug", and npm ls eddyter confirms it from the terminal. Release history lives on GitHub.
Start with What is Eddyter?, then Integrate Eddyter in 30 Minutes. First-time setup takes about 10 minutes.
0:00 — Title card. A search bar types out: "how you can upgrade eddyter." 0:05 — Card: "latest version." 0:06 — Version card: 1.4.24. 0:07 — Card: "a single command." 0:09 — The npm registry page for the eddyter package. Version 1.4.24, public, published 8 days ago. 84 versions, 18 dependencies, 1 dependent, 614 weekly downloads. Install command: npm i eddyter. Repository: github.com/EddyterAI/eddyter. Homepage: www.eddyter.com. 0:13 — Split screen. Left: Claude Code open on the Eventide event management web application. Right: the app running at localhost:3000, on the Notes > Create screen, with the Eddyter editor mounted in the note composer. The editor footer badge reads v1.4.23. 0:16 — Context from the previous session is visible: all 8 routes return 200, Eddyter authenticates cleanly on this origin, the editor mounts with its full 40-button toolbar and no license error. 0:20 — A new prompt is typed: "update eddyter to the latest version." 0:26 — The prompt is sent. 0:31 — Step: "Checking installed vs latest eddyter version." 0:37 — Result: installed 1.4.23, latest is 1.4.24. Plan stated — stop the dev server, update, then restart it. 0:39 — Step: "Type-check after eddyter update." 0:41 — The browser pane reloads the Eventide homepage: "Every unforgettable event starts here." 0:43 — Result: "Updated to 1.4.24 and types are clean. Restarting the server to verify the editor still works." 0:47 — The Notes composer reloads. The Eddyter editor shows its loading state, then mounts. 0:50 — The full toolbar is back. No license error, no config change, no code change anywhere in the project. 0:57 — The editor footer badge now reads v1.4.24. Upgrade complete. 1:00 — Outro: eddyter.com and eddyter.com/docs, with social links.
Run npm i eddyter@latest (or the yarn / pnpm equivalent), then restart your dev server. Stop the server before updating so the old module graph isn't held in memory. In the video the whole sequence runs from a single instruction inside Claude Code.
No. Going from 1.4.23 to 1.4.24 required no changes to ConfigurableEditorWithAuth, EditorProvider or any config file, and the type-check passed straight after the update. Patch releases are drop-in.
No. Your license key is bound to the origin you registered, not to a package version. What does break it is a changed origin — so if your key is registered against localhost:3000, pin your dev server to that port rather than letting it auto-assign.
The editor prints it in its own footer, next to "Report a Bug" — it reads v1.4.23 before the upgrade in this video and v1.4.24 after. From the terminal, npm ls eddyter gives you the same answer.
Eddyter, Upgrade, npm, Claude Code, Next.js
Paste a table into a plain text field and it flattens. Paste it into an editor and it arrives whole. This walkthrough does the same paste twice in one notes app, opens both results side by side, then switches the app to light mode and watches the editor re-theme itself.
Connect your own OpenAI, Anthropic, Gemini or Groq key and the editor's AI runs on your provider account at your rates. This walkthrough shows where the keys go, then generates a 500-word article with images from a single prompt.
