Skip to content

chore(deps): update dependency svelte to v5 [security] - #15

Open
renovate-appwrite[bot] wants to merge 1 commit into
masterfrom
renovate/npm-svelte-vulnerability
Open

renovate-appwrite[bot] wants to merge 1 commit into
masterfrom
renovate/npm-svelte-vulnerability

Conversation

@renovate-appwrite

@renovate-appwrite renovate-appwrite Bot commented Nov 3, 2026 •

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
svelte (source) ^3.0.0 → ^5.0.0 age confidence

Svelte vulnerable to XSS when using objects during server-side rendering

CVE-2022-25875 / GHSA-wv8q-r932-8hc7 / SNYK-JS-SVELTE-2931080

More information

Details

The package svelte before 3.49.0 is vulnerable to Cross-site Scripting (XSS) due to improper input sanitization and to improper escape of attributes when using objects during SSR (Server-Side Rendering). Exploiting this vulnerability is possible via objects with a custom toString() function.

Severity

  • CVSS Score: 6.1 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


svelte is vulnerable to XSS with textarea bind:value

GHSA-gw32-9rmw-qwww

More information

Details

Summary

A server-side rendered <textarea> with two-way bound value does not have its value correctly escaped in the rendered HTML.

Details

In SSR, <textarea bind:value={...}> does not have its value escaped when it is rendered into the HTML as <textarea>...</textarea>.

PoC

Put this in a server-side-rendered Svelte component:

<script>
  let value = `test'"></textarea><script` + `>alert('BIM');</sc` + `ript>`;
</script>

<textarea bind:value />
Impact
  • Only affects SSR
  • Needs a <textarea bind:value> filled by user content via two-way binding

Severity

  • CVSS Score: 8.4 / 10 (High)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:L/VA:N/SC:H/SI:H/SA:N

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


Svelte has a potential mXSS vulnerability due to improper HTML escaping

CVE-2024-45047 / GHSA-8266-84wp-wv5c

More information

Details

Summary

A potential XSS vulnerability exists in Svelte for versions prior to 4.2.19.

Details

Svelte improperly escapes HTML on server-side rendering. It converts strings according to the following rules:

  • If the string is an attribute value:
    • " -> &quot;
    • & -> &amp;
    • Other characters -> No conversion
  • Otherwise:
    • < -> &lt;
    • & -> &amp;
    • Other characters -> No conversion

The assumption is that attributes will always stay as such, but in some situation the final DOM tree rendered on browsers is different from what Svelte expects on server-side rendering. This may be leveraged to perform XSS attacks. More specifically, this can occur when injecting malicious content into an attribute within a <noscript> tag.

PoC

A vulnerable page (+page.svelte):

<script>
import { page } from "$app/stores"

// user input
let href = $page.url.searchParams.get("href") ?? "https://example.com";
</script>

<noscript>
  <a href={href}>test</a>
</noscript>

If a user accesses the following URL,

http://localhost:4173/?href=</noscript><script>alert(123)</script>

then, alert(123) will be executed.

Impact

XSS, when using an attribute within a noscript tag

Severity

  • CVSS Score: 5.1 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


Svelte SSR attribute spreading includes inherited properties from prototype chain

CVE-2026-27125 / GHSA-crpf-4hrx-3jrp

More information

Details

In server-side rendering, attribute spreading on elements (e.g. <div {...attrs}>) enumerates inherited properties from the object's prototype chain rather than only own properties. In environments where Object.prototype has already been polluted — a precondition outside of Svelte's control — this can cause unexpected attributes to appear in SSR output or cause SSR to throw errors. Client-side rendering is not affected.

Severity

  • CVSS Score: 5.3 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:H/SI:H/SA:N

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


Svelte affected by cross-site scripting via spread attributes in Svelte SSR

CVE-2026-27121 / GHSA-f7gr-6p89-r883

More information

Details

Versions of svelte prior to 5.51.5 are vulnerable to cross-site scripting (XSS) during server-side rendering. When using spread syntax to render attributes from untrusted data, event handler properties are included in the rendered HTML output. If an application spreads user-controlled or external data as element attributes, an attacker can inject malicious event handlers that execute in victims' browsers.

Severity

  • CVSS Score: 5.1 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:L/VI:N/VA:N/SC:H/SI:H/SA:N

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


Svelte SSR does not validate dynamic element tag names in <svelte:element>

CVE-2026-27122 / GHSA-m56q-vw4c-c2cp

More information

Details

When using <svelte:element this={tag}> in server-side rendering, the provided tag name is not validated or sanitized before being emitted into the HTML output. If the tag string contains unexpected characters, it can result in HTML injection in the SSR output. Client-side rendering is not affected.

Severity

  • CVSS Score: 5.1 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:L/VI:N/VA:N/SC:H/SI:H/SA:N

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


Svelte vulnerable to XSS during SSR with contenteditable bind:innerText and bind:textContent

CVE-2026-27901 / GHSA-phwv-c562-gvmh

More information

Details

The contents of bind:innerText and bind:textContent on contenteditable elements were not properly escaped. This could enable HTML injection and Cross-site Scripting (XSS) if rendering untrusted data as the binding's initial value on the server.

Severity

  • CVSS Score: 5.3 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:H/SI:H/SA:N

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


Svelte SSR vulnerable to cross-site scripting via spread attributes

CVE-2026-42599 / GHSA-pr6f-5x2q-rwfp

More information

Details

When using spread syntax to render attributes from untrusted data, event handler properties are included in the rendered HTML output. If an application spreads user-controlled or external data as element attributes, an attacker can inject malicious event handlers that execute in victims' browsers. Note that this vulnerability only triggers if the user's browser has JavaScript enabled but Svelte's hydration mechanism does not reach the vulnerable element before the event fires.

This is similar to but different from CVE-2026-27121.

Severity

  • CVSS Score: 5.1 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


Svelte Vulnerable to XSS via DOM Clobbering of Internal Framework State

CVE-2026-42573 / GHSA-rcqx-6q8c-2c42

More information

Details

Svelte was vulnerable to DOM clobbering of its internal framework state on elements, potentially leading to XSS attacks.

You are vulnerable if all of the following is true:

  • you are using attribute spreading on a form element
  • you are using attribute spreading or allow a dynamic value for the name attribute on an input or button element within that form
  • both of these are simultaneously user-controllable
<form {...spread1}>
  <input {...spread2}>
</form>

Severity

  • CVSS Score: 5.3 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:H/SI:H/SA:N

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


Release Notes

sveltejs/svelte (svelte)

v5.55.7

Compare Source

Patch Changes

v5.55.6

Compare Source

Patch Changes
  • fix: leave stale promises to wait for a later resolution, instead of rejecting (#​18180)

  • fix: keep dependencies of $state.eager/pending (#​18218)

  • fix: reapply context after transforming error during SSR (#​18099)

  • fix: don't rebase just-created batches (#​18117)

  • chore: allow null for pending in typings (#​18201)

  • fix: flush eager effects in production (#​18107)

  • fix: rethrow error of failed iterable after calling return() (#​18169)

  • fix: account for proxified instance when updating bind:this (#​18147)

  • fix: ensure scheduled batch is flushed if not obsolete (#​18131)

  • fix: resolve stale deriveds with latest value (#​18167)

  • chore: remove unnecessary increment_pending calls (#​18183)

  • fix: correctly compile component member expressions for SSR (#​18192)

  • fix: reset source.updated stack traces after flush (#​18196)

  • fix: replacing async 'blocking' strategy with 'merging' (#​18205)

  • fix: allow @debug tags to reference awaited variables (#​18138)

  • fix: re-run fallback props if dependencies update (#​18146)

  • fix: abort running obsolete async branches (#​18118)

  • fix: ignore comments when reading CSS values (#​18153)

  • fix: wrap Promise.all in save during SSR (#​18178)

  • fix: ignore false-positive errors of $inspect dependencies (#​18106)

v5.55.5

Compare Source

Patch Changes
  • fix: don't mark deriveds while an effect is updating (#​18124)

  • fix: do not dispatch introstart event with animation of animate directive (#​18122)

v5.55.4

Compare Source

Patch Changes
  • fix: never mark a child effect root as inert (#​18111)

  • fix: reset context after waiting on blockers of @const expressions (#​18100)

  • fix: keep flushing new eager effects (#​18102)

v5.55.3

Compare Source

Patch Changes
  • fix: ensure proper HMR updates for dynamic components (#​18079)

  • fix: correctly calculate @const blockers (#​18039)

  • fix: freeze deriveds once their containing effects are destroyed (#​17921)

  • fix: defer error boundary rendering in forks (#​18076)

  • fix: avoid false positives for reactivity loss warning (#​18088)

v5.55.2

Compare Source

Patch Changes
  • fix: invalidate @const tags based on visible references in legacy mode (#​18041)

  • fix: handle parens in template expressions more robustly (#​18075)

  • fix: disallow -- in idPrefix (#​18038)

  • fix: correct types for ontoggle on <details> elements (#​18063)

  • fix: don't override $destroy/set/on instance methods in dev mode (#​18034)

  • fix: unskip branches of earlier batches after commit (#​18048)

  • fix: never set derived.v inside fork (#​18037)

  • fix: skip rebase logic in non-async mode (#​18040)

  • fix: don't reset status of uninitialized deriveds (#​18054)

v5.55.1

Compare Source

Patch Changes
  • fix: unlink errored and otherwise finished batch (#​18264)

  • perf: walk composedPath() directly in delegated event propagation (#​18268)

  • fix: transfer effects when merging batches (#​18254)

  • fix: allow $derived(await ...) in disconnected effect roots (#​18273)

  • fix: remove temporary raw-text hydration markers (#​18269)

  • fix: propagate async @const blockers through closure references so template expressions like {(() => host)()} correctly wait for the awaited value (#​18309)

  • fix: properly unlink batches (#​18298)

  • fix: settle discarded batch (#​18290)

  • fix: declare let: directives before {@const} declarations on slotted elements (#​18271)

  • fix: resume outro-ed branches if they were kept around (#​18291)

  • fix: avoid waterfall-warning when async resolves to same value (#​18297)

  • fix: correctly coordinate component-level effects inside async blocks (#​18260)

  • fix: make unnecessary commit work less likely (#​18263)

  • chore: add tag name to a11y_click_events_have_key_events warning (#​18272)

  • fix: catch rejected promises while merging/committing (#​18266)

v5.55.0

Compare Source

Minor Changes
  • feat: export TweenOptions, SpringOptions, SpringUpdateOptions and Updater from svelte/motion (#​17967)
Patch Changes
  • fix: ensure HMR wrapper forwards correct start/end nodes to active effect (#​17985)

v5.54.1

Compare Source

Patch Changes
  • fix: hydration comments during hmr (#​17975)

  • fix: null out effect.b in destroy_effect (#​17980)

  • fix: group sync statements (#​17977)

  • fix: defer batch resolution until earlier intersecting batches have committed (#​17162)

  • fix: properly invoke iterator.return() during reactivity loss check (#​17966)

  • fix: remove trailing semicolon from {@​const} tag printer (#​17962)

v5.54.0

Compare Source

Minor Changes
  • feat: allow css, runes, customElement compiler options to be functions (#​17951)
Patch Changes
  • fix: reinstate reactivity loss tracking (#​17801)

v5.53.13

Compare Source

Patch Changes
  • fix: ensure $inspect after top level await doesn't break builds (#​17943)

  • fix: resume inert effects when they come from offscreen (#​17942)

  • fix: don't eagerly access not-yet-initialized functions in template (#​17938)

  • fix: discard batches made obsolete by commit (#​17934)

  • fix: ensure "is standalone child" is correctly reset (#​17944)

  • fix: remove nodes in boundary when work is pending and HMR is active (#​17932)

v5.53.12

Compare Source

Patch Changes
  • fix: update select.__value on change (#​17745)

  • chore: add invariant helper for debugging (#​17929)

  • fix: ensure deriveds values are correct across batches (#​17917)

  • fix: handle async RHS in assignment_value_stale (#​17925)

  • fix: avoid traversing clean roots (#​17928)

v5.53.11

Compare Source

Patch Changes
  • fix: remove untrack circular dependency (#​17910)

  • fix: recover from errors that leave a corrupted effect tree (#​17888)

  • fix: properly lazily evaluate RHS when checking for assignment_value_stale (#​17906)

  • fix: resolve boundary in correct batch when hydrating (#​17914)

  • chore: rebase batches after process, not during (#​17900)

v5.53.10

Compare Source

Patch Changes
  • fix: re-process batch if new root effects were scheduled (#​17895)

v5.53.9

Compare Source

Patch Changes
  • fix: better bind:this cleanup timing (#​17885)

v5.53.8

Compare Source

Patch Changes
  • fix: {@html} no longer duplicates content inside contenteditable elements (#​17853)

  • fix: don't access inert block effects (#​17882)

  • fix: handle asnyc updates within pending boundary (#​17873)

  • perf: avoid re-traversing the effect tree after $: assignments (#​17848)

  • chore: simplify scheduling logic (#​17805)

v5.53.7

Compare Source

Patch Changes
  • fix: correctly add __svelte_meta after else-if chains (#​17830)

  • perf: cache element interactivity and source line splitting in compiler (#​17839)

  • chore: avoid rescheduling effects during branch commit (#​17837)

  • perf: optimize CSS selector pruning (#​17846)

  • fix: preserve original boundary errors when keyed each rows are removed during async updates (#​17843)

  • perf: avoid O(n²) name scanning in scope generate and unique (#​17844)

  • fix: preserve each items that are needed by pending batches (#​17819)

v5.53.6

Compare Source

Patch Changes
  • perf: optimize parser hot paths for faster compilation (#​17811)

  • fix: SvelteMap incorrectly handles keys with undefined values (#​17826)

  • fix: SvelteURL search setter now returns the normalized value, matching native URL behavior (#​17828)

  • fix: visit synthetic value node during ssr (#​17824)

  • fix: always case insensitive event handlers during ssr (#​17822)

  • chore: more efficient effect scheduling (#​17808)

  • perf: optimize compiler analysis phase (#​17823)

  • fix: skip redundant batch.apply (#​17816)

  • chore: null out current_batch before committing branches (#​17809)

v5.53.5

Compare Source

Patch Changes

v5.53.4

Compare Source

Patch Changes
  • fix: set server context after async transformError (#​17799)

  • fix: hydrate if blocks correctly (#​17784)

  • fix: handle default parameters scope leaks (#​17788)

  • fix: prevent flushed effects from running again (#​17787)

v5.53.3

Compare Source

Patch Changes
  • fix: render :catch of #await block with correct key (#​17769)

  • chore: pin aria-query@​5.3.1 (#​17772)

  • fix: make string coercion consistent to toString (#​17774)

v5.53.2

Compare Source

Patch Changes
  • fix: update expressions on server deriveds (#​17767)

  • fix: further obfuscate node:crypto import from overzealous static analysis (#​17763)

v5.53.1

Compare Source

Patch Changes
  • fix: ensure $inspect after top level await doesn't break builds (#​17943)

  • fix: resume inert effects when they come from offscreen (#​17942)

  • fix: don't eagerly access not-yet-initialized functions in template (#​17938)

  • fix: discard batches made obsolete by commit (#​17934)

  • fix: ensure "is standalone child" is correctly reset (#​17944)

  • fix: remove nodes in boundary when work is pending and HMR is active (#​17932)

v5.53.0

Compare Source

Minor Changes
  • feat: allow comments in tags (#​17671)

  • feat: allow error boundaries to work on the server (#​17672)

Patch Changes
  • fix: use TrustedHTML to test for customizable <select> support, where necessary (#​17743)

  • fix: ensure head effects are kept in the effect tree (#​17746)

  • chore: deactivate current_batch by default in unset_context (#​17738)

v5.52.0

Compare Source

Minor Changes
  • feat: support TrustedHTML in {@html} expressions (#​17701)
Patch Changes
  • fix: repair dynamic component truthy/falsy hydration mismatches (#​17737)

  • fix: re-run non-render-bound deriveds on the server (#​17674)

v5.51.5

Compare Source

Patch Changes

v5.51.4

Compare Source

Patch Changes
  • chore: proactively defer effects in pending boundary (#​17734)

  • fix: detect and error on non-idempotent each block keys in dev mode (#​17732)

v5.51.3

Compare Source

Patch Changes
  • fix: prevent event delegation logic conflicting between svelte instances (#​17728)

  • fix: treat CSS attribute selectors as case-insensitive for HTML enumerated attributes (#​17712)

  • fix: locate Rollup annontaion friendly to JS downgraders (#​17724)

  • fix: run effects in pending snippets (#​17719)

v5.51.2

Compare Source

Patch Changes
  • fix: take async into consideration for dev delegated handlers (#​17710)

  • fix: emit state_referenced_locally warning for non-destructured props (#​17708)

v5.51.1

Compare Source

Patch Changes
  • fix: don't crash on undefined document.contentType (#​17707)

  • fix: use symbols for encapsulated event delegation (#​17703)

v5.51.0

Compare Source

Minor Changes
  • feat: Use TrustedTypes for HTML handling where supported (#​16271)
Patch Changes
  • fix: sanitize template-literal-special-characters in SSR attribute values (#​17692)

  • fix: follow-up formatting in print() — flush block-level elements into separate sequences (#​17699)

  • fix: preserve delegated event handlers as long as one or more root components are using them (#​17695)

v5.50.3

Compare Source

Patch Changes
  • fix: take into account nodeName case sensitivity on XHTML pages (#​17689)

  • fix: render multiple and selected attributes as empty strings for XHTML compliance (#​17689)

  • fix: always lowercase HTML elements, for XHTML compliance (#​17664)

  • fix: freeze effects-inside-deriveds when disconnecting, unfreeze on reconnect (#​17682)

  • fix: propagate $effect errors to <svelte:boundary> (#​17684)

v5.50.2

Compare Source

Patch Changes
  • fix: resolve effect_update_depth_exceeded when using bind:value on <select> with derived state in legacy mode (#​17645)

  • fix: don't swallow DOMException when media.play() fails in bind:paused (#​17656)

  • chore: provide proper public type for parseCss result (#​17654)

  • fix: robustify blocker calculation (#​17676)

  • fix: reduce if block nesting (#​17662)

v5.50.1

Compare Source

Patch Changes
  • fix: render boolean attribute values as empty strings for XHTML compliance (#​17648)

  • fix: prevent async render tag hydration mismatches (#​17652)

v5.50.0

Compare Source

Minor Changes
  • feat: allow use of createContext when instantiating components programmatically (#​17575)
Patch Changes
  • fix: ensure infinite effect loops are cleared after flushing (#​17601)

  • fix: allow {#key NaN} (#​17642)

  • fix: detect store in each block expression regardless of AST shape (#​17636)

  • fix: treat <menu> like <ul>/<ol> for a11y role checks (#​17638)

  • fix: add vite-ignore comment inside dynamic crypto import (#​17623)

  • chore: wrap JSDoc URLs in @see and @link tags (#​17617)

  • fix: properly hydrate already-resolved async blocks (#​17641)

  • fix: emit each_key_duplicate error in production (#​16724)

  • fix: exit resolved async blocks on correct node when hydrating (#​17640)

v5.49.2

Compare Source

Patch Changes
  • chore: remove SvelteKit data attributes from elements.d.ts (#​17613)

  • fix: avoid erroneous async derived expressions for blocks (#​17604)

  • fix: avoid Cloudflare warnings about not having the "node:crypto" module ([#​17612](https://redirect.github.

[!IMPORTANT]
✂ PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@ghost

ghost commented Nov 3, 2026 •

Copy link
Copy Markdown

🟡 Tier B · Needs changes before merging

The remaining open example-auth finding is still reproducible: npm run build fails because rollup-plugin-svelte imports an unexported svelte/compiler.js subpath.

This PR upgrades Svelte to v5 across the Svelte examples and refreshes example-auth's lockfile with Svelte's new transitive dependencies. The SSR project also has a lockfile and checker version aligned with its Svelte 5 manifest.

Verdict New comments Fixed Still open
💬 Commented 0 2 1
Fix with agent prompt
### Issue 1
example-auth/package-lock.json:789
**Svelte 5 breaks the example-auth build**

With the locked Svelte 5.57.3, `npm run build` fails because `rollup-plugin-svelte` 6.0.0 imports `svelte/compiler.js`, which Svelte 5 does not export. The example-auth project no longer builds with this dependency combination.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.
📂 Walkthrough · 2
File Change
example-auth/package.json Updates the example-auth Svelte dependency to v5.
example-auth/package-lock.json Locks Svelte 5.57.3 and its new transitive dependencies.
⏳ Still open from earlier reviews · 1
✅ Fixed since the last review · 2
  • Update the SSR project's lockfile with the Svelte bump · server-side-rendering/package.json:19
  • Svelte 5 breaks the SSR check script · server-side-rendering/package.json:19

Reviewed c611bc3 · Details · Comment @hansi-codes review to re-run, or mention @hansi-codes with a question.

@ghost ghost left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Tier B · 3 blocking findings to address. Summary

Comment thread server-side-rendering/package.json Resolved
Comment thread server-side-rendering/package.json Resolved
"resolved": "https://registry.npmjs.org/svelte/-/svelte-3.24.1.tgz",
"integrity": "sha512-OX/IBVUJSFo1rnznXdwf9rv6LReJ3qQ0PwRjj76vfUWyTfbHbR9OXqJBnUrpjyis2dwYcbT2Zm1DFjOOF1ZbbQ==",
"dev": true
"version": "5.57.3",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Svelte 5 breaks the example-auth build

With the locked Svelte 5.57.3, npm run build fails because rollup-plugin-svelte 6.0.0 imports svelte/compiler.js, which Svelte 5 does not export. The example-auth project no longer builds with this dependency combination.

Prompt To Fix With AI
This is a comment left during a code review.
Path: example-auth/package-lock.json
Line: 789

Comment:
**Svelte 5 breaks the example-auth build**

With the locked Svelte 5.57.3, `npm run build` fails because `rollup-plugin-svelte` 6.0.0 imports `svelte/compiler.js`, which Svelte 5 does not export. The example-auth project no longer builds with this dependency combination.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

🟠 Major · bug · Reply if this doesn't apply.

@renovate-appwrite
renovate-appwrite Bot force-pushed the renovate/npm-svelte-vulnerability branch from c611bc3 to 5203ec8 Compare November 10, 2026 06:39
@appwrite

appwrite Bot commented Nov 10, 2026 •

Copy link
Copy Markdown

🟡 Tier B · Needs changes before merging

The dependency bump makes the example build fail, and its unchanged component-instantiation call is incompatible with Svelte 5 by default.

This updates the example-auth Svelte dependency from v3 to v5 and refreshes its npm lockfile to Svelte 5.57.3 and the associated compiler dependencies. The upgraded Svelte version includes the SSR security fixes described in the dependency update.

Verdict New comments Fixed Still open
🛑 Changes requested 2 0 0
Finding Where
🟠 Svelte 5 breaks the existing Rollup build example-auth/package.json:16
🟠 The app still constructs Svelte components with new example-auth/package.json:16
Fix with agent prompt
### Issue 1
example-auth/package.json:16
**Svelte 5 breaks the existing Rollup build**

I ran `npm ci` successfully, but `npm run build` fails because the unchanged `rollup-plugin-svelte` 6.0.0 resolves `svelte/compiler.js`, which Svelte 5 no longer exports. The example cannot produce a bundle with this dependency combination; update the compiler integration or keep a compatible Svelte version.

### Issue 2
example-auth/package.json:16
**The app still constructs Svelte components with `new`**

After the build integration is made compatible, `example-auth/src/main.js:10` still mounts the component with `new App(...)`. Svelte 5 components are not constructors by default, so the app will throw instead of mounting unless the entry point is migrated to `mount` or the compiler enables `compatibility.componentApi: 4`.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.
📂 Walkthrough · 2
File Change
example-auth/package.json Bumps the example's Svelte dependency range to v5.
example-auth/package-lock.json Refreshes the lockfile to npm lockfile v3 and pins Svelte 5.57.3 with its updated dependencies.

Reviewed 5203ec8 · Details · Comment @appwrite review to re-run, or mention @appwrite with a question.

@appwrite appwrite Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Tier B · 2 blocking findings to address. Summary

Comment thread example-auth/package.json
"rollup-plugin-svelte": "^6.0.0",
"rollup-plugin-terser": "^7.0.0",
"svelte": "^3.0.0"
"svelte": "^5.0.0"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Svelte 5 breaks the existing Rollup build

I ran npm ci successfully, but npm run build fails because the unchanged rollup-plugin-svelte 6.0.0 resolves svelte/compiler.js, which Svelte 5 no longer exports. The example cannot produce a bundle with this dependency combination; update the compiler integration or keep a compatible Svelte version.

Prompt To Fix With AI
This is a comment left during a code review.
Path: example-auth/package.json
Line: 16

Comment:
**Svelte 5 breaks the existing Rollup build**

I ran `npm ci` successfully, but `npm run build` fails because the unchanged `rollup-plugin-svelte` 6.0.0 resolves `svelte/compiler.js`, which Svelte 5 no longer exports. The example cannot produce a bundle with this dependency combination; update the compiler integration or keep a compatible Svelte version.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

🟠 Major · bug · Reply if this doesn't apply.

Comment thread example-auth/package.json
"rollup-plugin-svelte": "^6.0.0",
"rollup-plugin-terser": "^7.0.0",
"svelte": "^3.0.0"
"svelte": "^5.0.0"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The app still constructs Svelte components with new

After the build integration is made compatible, example-auth/src/main.js:10 still mounts the component with new App(...). Svelte 5 components are not constructors by default, so the app will throw instead of mounting unless the entry point is migrated to mount or the compiler enables compatibility.componentApi: 4.

Prompt To Fix With AI
This is a comment left during a code review.
Path: example-auth/package.json
Line: 16

Comment:
**The app still constructs Svelte components with `new`**

After the build integration is made compatible, `example-auth/src/main.js:10` still mounts the component with `new App(...)`. Svelte 5 components are not constructors by default, so the app will throw instead of mounting unless the entry point is migrated to `mount` or the compiler enables `compatibility.componentApi: 4`.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

🟠 Major · bug · Reply if this doesn't apply.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants