BluetOpen source

What agents should know before contributing

sveltejs/svelte

web development for the rest of us

Read by Bluet from 2 files written for agents and 300 merged pull requests on 2026-09-25. Not reviewed by the maintainers.

Rules its files tell agents (2)

  • shouldDon't take this personally if this happens, and feel free to open a new issue once you've gathered all the inf…

    When opening a new issue, always make sure to fill out the issue template. This step is very important! Not doing so may result in your issue not being managed in a timely fashion. Don't take this personally if this happens, and feel free to open a new issue once you've gathered all the information required by the template.

    CONTRIBUTING.md
  • shouldDO NOT submit a PR without running the full test suite.

    When submitting a PR, you MUST read PULL_REQUEST_TEMPLATE.md and fill it out correctly. DO NOT submit a PR without running the full test suite.

    AGENTS.md

Decisions its pull requests settled (40)

  • #18147account for proxified instance when updating `bind:this`
  • #18075handle parens in template expressions more robustly
  • #18181wait with resolving prior batches until current one commits
  • #18180leave stale promises to wait for a later resolution, instead of rejecting
  • #18167resolve stale deriveds with latest value
  • #18196remove `source.updated` stack traces after `flush`
  • #18218keep dependencies of `$state.eager`/`pending` (alternative approach)
  • #18205treat batches as a linked list
  • #18303prevent batch unlinking twice
  • #18263make unnecessary commit work less likely
  • #18238use named symbols everywhere
  • #18226clarify context state getter pattern
  • #18345set input type before spread value
  • #18330don't mistake `type` identifier expressions for TS `type` declarations in tags
  • #18320deduplicate identical hoisted templates within a component
  • #18430avoid NaN keyframe values in slide transition
  • #18400abort deriveds own AbortSignal when it disconnects
  • #18425make `SvelteURLSearchParams` notifications accurate
  • #18477clarify $bindable fallback binding requirement
  • #18431don't resurrect outroing elements when an ancestor block is paused and resumed
  • #18466distinct memoizer on style/class directives
  • #18521transform computed keys in keyed each block destructuring patterns
  • #18533block declaration tags on async values read inside closures
  • #18525skip unnecessary derived effect in earlier batch
  • #18540avoid css tree-shaking for exported Snippet
  • #18541clear previous_task reference after abort in Tween
  • #18534clarify when `$effect.pre` runs relative to DOM updates
  • #18556call `onerror` and provide a working `reset` when hydrating a failed boundary
  • #18569release last_propagated_event after event propagation settles
  • #18550in non-async mode, only push variable to current_sources when active_reaction is updating
  • #18594preserve logical assignments to private state fields
  • #18597note that transitions bypass CSS prefers-reduced-motion
  • #18613treat concise arrow function bodies as implicit returns when calculating blockers
  • #18581clarify that context lookup includes the current component and all ancestors
  • #18618remove stale capture listeners from spread attributes
  • #18614append_styles resolving to `document.head` in WC
  • #18616preserve renderer type in copy() during SSR
  • #18620give effect teardowns the value from before the first write in a flush
  • #18625skip controlled each fast path while another batch is pending
  • #18634apply CSS custom properties with falsy values on components
Your agents can be told this before they touch the code. Get it for your repository: npx bluet-mcp init. What Bluet is.
sveltejs/svelte: what agents should know before contributing · Bluet