You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Simon H a60995abef fix: allow async `{@const}` in more places (#16643) ... Implemented by reusing the `async_body` function inside `Fragment.js`. Also removes the ability to reference a `{@const ...}` of an implicit child inside a boundary pending/failed snippet: - existing duplication of consts can have unintended side effects, e.g. async consts would unexpectedly called multiple times - what if a const is the reason for the failure of a boundary, but is then referenced in the failed snippet? - what if an async const is referenced in a pending snippet? deadlock - inconsistent with how it behaves for components where this already does not work Implemented via the experimental flag so the behavior change only applies there as this is a breaking change strictly speaking. Also added a compiler error for this. closes #16462		2 weeks ago
..
client-errors.md	fix: robustify reset calls in error boundaries (#16171)	2 months ago
client-warnings.md	fix: robustify reset calls in error boundaries (#16171)	2 months ago
compile-errors.md	fix: allow async `{@const}` in more places (#16643)	2 weeks ago
compile-warnings.md	docs: corrections (#16550)	1 month ago
server-errors.md	docs: more details for errors/warnings on the site (#14632)	9 months ago
shared-errors.md	feat: allow `await` in components (#15844)	2 months ago
shared-warnings.md	fix docs (#14635)	9 months ago