Skip to content

Commit 9a91267

Browse files
authored
Merge branch 'sveltejs:main' into fix/async-const-in-boudary
2 parents bde563b + e0dba16 commit 9a91267

File tree

6 files changed

+194
-258
lines changed

6 files changed

+194
-258
lines changed

.github/workflows/ecosystem-ci-trigger.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,8 @@ on:
44
issue_comment:
55
types: [created]
66

7+
permissions: {}
8+
79
jobs:
810
trigger:
911
runs-on: ubuntu-latest

.github/workflows/pkg.pr.new.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,8 @@
11
name: Publish Any Commit
22
on: [push, pull_request]
33

4+
permissions: {}
5+
46
jobs:
57
build:
68
permissions: {}

documentation/docs/03-template-syntax/19-await-expressions.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -139,8 +139,6 @@ If a `<svelte:boundary>` with a `pending` snippet is encountered during SSR, tha
139139

140140
As an experimental feature, the details of how `await` is handled (and related APIs like `$effect.pending()`) are subject to breaking changes outside of a semver major release, though we intend to keep such changes to a bare minimum.
141141

142-
Currently, server-side rendering is synchronous. If a `<svelte:boundary>` with a `pending` snippet is encountered during SSR, only the `pending` snippet will be rendered.
143-
144142
## Breaking changes
145143

146144
Effects run in a slightly different order when the `experimental.async` option is `true`. Specifically, _block_ effects like `{#if ...}` and `{#each ...}` now run before an `$effect.pre` or `beforeUpdate` in the same component, which means that in [very rare situations](/playground/untitled?#H4sIAAAAAAAAE22R3VLDIBCFX2WLvUhnTHsf0zre-Q7WmfwtFV2BgU1rJ5N3F0jaOuoVcPbw7VkYhK4_URTiGYkMnIyjDjLsFGO3EvdCKkIvipdB8NlGXxSCPt96snbtj0gctab2-J_eGs2oOWBE6VunLO_2es-EDKZ5x5ZhC0vPNWM2gHXGouNzAex6hHH1cPHil_Lsb95YT9VQX6KUAbS2DrNsBdsdDFHe8_XSYjH1SrhELTe3MLpsemajweiWVPuxHSbKNd-8eQTdE0EBf4OOaSg2hwNhhE_ABB_ulJzjj9FULvIcqgm5vnAqUB7wWFMfhuugQWkcAr8hVD-mq8D12kOep24J_IszToOXdveGDsuNnZwbJUNlXsKnhJdhUcTo42s41YpOSneikDV5HL8BktM6yRcCAAA=) it is possible to update a block that should no longer exist, but only if you update state inside an effect, [which you should avoid]($effect#When-not-to-use-$effect).

package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@
2626
"bench:debug": "node --allow-natives-syntax --inspect-brk ./benchmarking/run.js"
2727
},
2828
"devDependencies": {
29-
"@changesets/cli": "^2.27.8",
29+
"@changesets/cli": "^2.29.7",
3030
"@sveltejs/eslint-config": "^8.3.3",
3131
"@svitejs/changesets-changelog-github-compact": "^1.1.0",
3232
"@types/node": "^20.11.5",

packages/svelte/package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -158,7 +158,7 @@
158158
"@types/aria-query": "^5.0.4",
159159
"@types/node": "^20.11.5",
160160
"dts-buddy": "^0.5.5",
161-
"esbuild": "^0.21.5",
161+
"esbuild": "^0.25.10",
162162
"rollup": "^4.22.4",
163163
"source-map": "^0.7.4",
164164
"tinyglobby": "^0.2.12",

0 commit comments

Comments
 (0)