Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also orlearn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also.Learn more about diff comparisons here.
base repository:sveltejs/svelte
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base:svelte@5.43.10
Choose a base ref
Loading
...
head repository:sveltejs/svelte
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare:svelte@5.43.11
Choose a head ref
Loading
  • 3commits
  • 11files changed
  • 3contributors

Commits on Nov 18, 2025

  1. perf: don't use tracing overeager during dev (#17183)

    * perf: don't use tracing overeager during dev#17176 is a case where many sources are created and then written to (due to Svelte 4 prop mechanics), and our tracing kicked in eagerly. That combined with the excessive depth of the related stack traces slowed things down tremendously.The fix is simple: Don't record stack traces until we've seen this source get updated for a couple of times. Additionally we now delete the `updates` map after a flush. Previously it was just an ever-growing stack trace map.* fix* fix
    @dummdidumm
    dummdidumm authoredNov 18, 2025
    Configuration menu
    Copy the full SHA
    ebb97a6View commit details
    Browse the repository at this point in the history

  2. fix: don't cancel transition of already outroing elements (#17186)

    * fix: don't cancel transition of already outroing elements#16977 forgot one detail: While an element is outroing, the block of e.g. an if block can be triggered again, resolving to the same condition. In that case we have an in-between state where the element is still onscreen but already outroing. We have to detect this to not eagerly destroy the corresponding effect when we arrive at the outro/destroy logic.Fixes#16982* fix---------Co-authored-by: Rich Harris <rich.harris@vercel.com>
    @dummdidumm@Rich-Harris
    dummdidumm andRich-Harris authoredNov 18, 2025
    Configuration menu
    Copy the full SHA
    203c228View commit details
    Browse the repository at this point in the history

  3. Version Packages (#17189)

    Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
    @github-actions
    github-actions[bot] authoredNov 18, 2025
    Configuration menu
    Copy the full SHA
    92c936dView commit details
    Browse the repository at this point in the history
Loading
[8]ページ先頭
©2009-2025 Movatter.jp