[MeritonPylla]

The examples catalog has React and vanilla quickstarts, but no SvelteKit starter. This adds one under examples/sveltekit.

The part worth a look is SSR. SuperDoc only runs in the browser, so if it loads during SSR you get document is not defined. I didn't want to turn SSR off for the whole app, so I set ssr = false on just the editor route and mount the editor in a client-only $effect. Everything else in an app keeps server rendering.

Registered it like the other v2 examples: examples/README.md, go-links/links.json, and published-routes.json.

Tested locally: typecheck / build / Playwright smoke pass, and it renders a real .docx with a clean console.

Re-opened against main for v2 after #3858 (which targeted v1) was closed.

[cubic-dev-ai]

All reported issues were addressed across 17 files

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[MeritonPylla]

@caio-pizzol following up on your note on #3858: this is the SvelteKit starter reopened against main for v2. lmk what u think

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

---

View medium (1)

🟠 **Medium**

1. Readiness remains enabled after failure 🐞

Description

After the editor has opened, onException no longer clears ready, so the Export DOCX button
remains enabled even when SuperDoc reports an exception that may invalidate the active editor. This
allows users to attempt export from an errored editor and can produce a failed, empty, or stale
download.

Code

examples/sveltekit/src/routes/+page.svelte[R29-32]

+        if (!opened) {
+          loadFailed = true;
+          if (active) ready = false;
+        }

Evidence

The exception handler only sets ready = false when opened is false. Once onReady sets `opened
= true and ready = true`, a later exception leaves both the readiness flag and the export button
enabled; the button's disabled expression directly depends on ready.

examples/sveltekit/src/routes/+page.svelte[23-34]
examples/sveltekit/src/routes/+page.svelte[64-67]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
A SuperDoc exception received after `onReady` leaves `ready` set to true because the handler only clears it while `opened` is false. The export button therefore remains enabled after an exception that may make the editor no longer exportable.

## Issue Context
The button at `examples/sveltekit/src/routes/+page.svelte[65-67]` is disabled solely from `!ready || exporting`. Preserve any intended recoverable-exception behavior, but ensure exceptions classified as fatal invalidate readiness.

## Fix Focus Areas
- examples/sveltekit/src/routes/+page.svelte[28-34]
- examples/sveltekit/src/routes/+page.svelte[64-67]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

---

Context

Review mode: ⚖️ Balanced: This push changes the SvelteKit SSR boundary and Vite dependency optimization, creating runtime/build behavior risks that warrant a complete single-pass review, though it is not dense enough for extended.

---

Tip of the day

💡 Did you know, you can enable the Remediation agent and Qodo fixes findings in a dedicated fix PR

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

---

Previous review results

Review updated until commit 45cdd1d ⚖️ Balanced

Results up to commit 5de01d1 🚀 Fast

🐞 Bugs (1) 📘 Rule violations (0) 📎 Requirement gaps (0) 🎨 UX issues (0) 📜 Skill insights (0)

---

View medium (1)

🟠 **Medium**

1. Readiness remains enabled after failure 🐞

Description

After the editor has opened, onException no longer clears ready, so the Export DOCX button
remains enabled even when SuperDoc reports an exception that may invalidate the active editor. This
allows users to attempt export from an errored editor and can produce a failed, empty, or stale
download.

Code

examples/sveltekit/src/routes/+page.svelte[R29-32]

+        if (!opened) {
+          loadFailed = true;
+          if (active) ready = false;
+        }

Evidence

The exception handler only sets ready = false when opened is false. Once onReady sets `opened
= true and ready = true`, a later exception leaves both the readiness flag and the export button
enabled; the button's disabled expression directly depends on ready.

examples/sveltekit/src/routes/+page.svelte[23-34]
examples/sveltekit/src/routes/+page.svelte[64-67]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
A SuperDoc exception received after `onReady` leaves `ready` set to true because the handler only clears it while `opened` is false. The export button therefore remains enabled after an exception that may make the editor no longer exportable.

## Issue Context
The button at `examples/sveltekit/src/routes/+page.svelte[65-67]` is disabled solely from `!ready || exporting`. Preserve any intended recoverable-exception behavior, but ensure exceptions classified as fatal invalidate readiness.

## Fix Focus Areas
- examples/sveltekit/src/routes/+page.svelte[28-34]
- examples/sveltekit/src/routes/+page.svelte[64-67]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

---

Powered by Qodo

[caio-pizzol]

Thanks for the contribution, @MeritonPylla! I pushed a few small updates to keep this consistent with our other quickstarts:

• Kept SSR enabled since SuperDoc starts inside $effect.
• Fixed pnpm dev so the document worker loads correctly.
• Updated the README and test to match.

Everything is working locally. We’ll wait for CI and then this should be ready.

[MeritonPylla]

Thanks for the contribution, @MeritonPylla! I pushed a few small updates to keep this consistent with our other quickstarts:

• Kept SSR enabled since SuperDoc starts inside $effect.
• Fixed pnpm dev so the document worker loads correctly.
• Updated the README and test to match.

Everything is working locally. We’ll wait for CI and then this should be ready.

Looking good, thanks to you too