msb-public/svelte - svelte - 马士兵教育代码仓库

Author	SHA1	Message	Date
Rich Harris	3289ac3ad1	slightly better waterfall warning	7 months ago
Rich Harris	148ffd2783	warn on reactivity loss	7 months ago
Rich Harris	118e28445d	experimental waterfall detection	7 months ago
Rich Harris	76ce303b0a	chore: bump esrap (#14969 ) * chore: bump esrap * fix * bump again	8 months ago
Rich Harris	d41801c75f	feat: warn on using `slide` transition with invalid `display` styles (#14936 ) * feat: warn on using `slide` transition with table elements * more generic * more generic	8 months ago
Simon H	68d266e0f8	fix: remove overzealous `reactive_declaration_non_reactive_property` warning (#14663 ) fixes #14532 This removes the `reactive_declaration_non_reactive_property` warning altogether. The first version caused many false positives at compile time. The refined runtime version (introduced in #14192) was hoped to fix this, but it turns out we now get loads of false positives at runtime.	9 months ago
Simon H	cfc1fb7de8	chore: provide links to documentation for errors/warnings (#14629 ) * chore: provide links to documentation for errors/warnings closes #11305 * changeset * fix most of the tests * fix mutations messing with nodes between runs * more concise * more test fixes * last one	9 months ago
Rich Harris	fe0bd299a5	fix: proxify values when assigning using `\|\|=`, `&&=` and `??=` operators (#14273 ) * add failing test for #14268 * simplify * proxify values when using \|\|=, &&= and ??= assignment operators * proxify values assigned to private state fields * changeset * fix * fix * add warning * update test	9 months ago
Rich Harris	a5de086f95	feat: turn `reactive_declaration_non_reactive_property` into a runtime warning (#14192 ) * turn `reactive_declaration_non_reactive_property` into a runtime warning * ignore warning * Update packages/svelte/src/internal/client/reactivity/effects.js Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com> * Update packages/svelte/src/internal/client/runtime.js Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com> * fix * test * changeset * Update .changeset/witty-turtles-bake.md Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com> * add some details * check * regenerate --------- Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com>	9 months ago
Paolo Ricciuti	8ff2af52d3	fix: show filename information in `legacy_recursive_reactive_block` (#13764 )	11 months ago
Dominic Gannaway	139114bdcb	fix: ensure legacy run utility does not cause cycles (#13643 ) * fix: ensure legacy run utility does not cause cycles * add warning * add warning * lint * feedback * lint * lint	11 months ago
Simon H	ed7611b163	feat: provide guidance in browser console when logging `$state` objects (#13142 ) * feat: provide guidance in browser console when logging `$state` objects Wrap console.log/warn/error statements in DEV mode with a check whether or not they contain state objects. Closes #13123 This is an alternative or enhancement to #13070. Alternative if we deem it the better solution. Enhancement because it's not as robust as a custom formatter: We only check the top level of each entry (though we could maybe traverse a few levels), and if you're logging class instances, snapshot currently stops at the boundaries there and so you don't get snapshotted values for these (arguably this is a more general problem of $inspect and $state.snapshot), whereas with custom formatter it doesn't matter at which level you come across it. * lint * use normal warning mechanism, so we can link to docs etc * add a few more methods --------- Co-authored-by: Rich Harris <rich.harris@vercel.com>	12 months ago
Rich Harris	0812b10100	breaking: overhaul proxies, remove `$state.is` (#12916 ) * chore: use closures for state proxies * use variables * early return * tidy up * move ownership stuff into separate object * put original value directly on STATE_SYMBOL * rename * tidy up * tidy * tweak * fix * remove is_frozen check * remove `$state.is` * avoid mutations * tweak * changesets * changeset * changeset * regenerate * add comment * add note * add test	1 year ago
Rich Harris	c51dfcfc00	feat: warn on invalid event handlers (#12818 ) * feat: warn on invalid event handlers * handle assignments etc * handle component events too where possible * lint	1 year ago
Simon H	3515776009	docs: tweak `$state.is` warning (#12599 ) Also add a detailed explanation which can later appear on the docs site closes #11556	1 year ago
Dominic Gannaway	518d9854f5	chore: add warning for invalid render function of createRawSnippet (#12535 ) * chore: add warning for invalid render function of createRawSnippet * add test * warnings * Update packages/svelte/messages/client-warnings/warnings.md Co-authored-by: Rich Harris <rich.harris@vercel.com> * build * build * build --------- Co-authored-by: Rich Harris <rich.harris@vercel.com>	1 year ago
Rich Harris	2ce2b7d98b	feat: warn if binding to a non-reactive property (#12500 ) * feat: warn if binding to a non-reactive property * tweak	1 year ago
Paolo Ricciuti	4e8d1c8c52	feat: runtime dev warn for mismatched `@html` (#12396 ) * feat: runtime dev warn for mismatched `@html` * fix: limit the length of the client value shown in the error * put logic inside a helper * remove $.hash, no longer needed * fix * tweak * update changeset * fix --------- Co-authored-by: Rich Harris <rich.harris@vercel.com>	1 year ago
Rich Harris	29ca451c9e	chore: tidier generated message code (#12062 ) * chore: tidier generated message code * lint	1 year ago
Rich Harris	2ebb277be7	feat: more information when hydration fails (#11649 ) In the case of an invalid child element, we already get information about the parent and the child, but in other cases where a mismatch could occur you're pretty much on your own. This adds a bit more context to hydration_mismatch warnings — 'The error occurred near ...'	1 year ago
Dominic Gannaway	7ef686f8ee	feat: provide $state warnings for accidental equality (#11610 ) * feat: provide $state warnings for accidental equality * tune * tune * tune * adjust test * fix treeshaking * fix bugs * fix bugs * refactor * revert test changes * tune * tune * tune * tune * fix up * fix * remove if(DEV) stuff * use console.trace, like we do for ownership warnings * tweak * tweak message, simplify logic --------- Co-authored-by: Rich Harris <rich.harris@vercel.com>	1 year ago
Rich Harris	8e17428316	chore: tidy up messages (#11327 ) * start reorganising messages * tidy up * more * more * more * alphabetise * consolidate * more * more * more * more * more * more * alphabetise * more * this is no longer needed * no longer necessary * more * more * fix * regenerate messages * more * more * tighten up rune validation * more * fix * more * tweak a11y messages * add server errors * overhaul runtime errors * regenerate messages * unused * lint * more * more * Update packages/svelte/messages/compile-errors/script.md Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com> * Update packages/svelte/messages/client-warnings/warnings.md Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com> * fix --------- Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com>	1 year ago
Rich Harris	6ad5cd4461	feat: implement message overloads (#11318 )	1 year ago
Rich Harris	476f2172b6	fix: mark `accessors` and `immutable` as deprecated (#11277 ) * fix: mark `accessors` and `immutable` as deprecated * add warnings for deprecated <svelte:options> attributes * disable accessors in runes mode * update tests * tidy up * the hell? * regenerate types * if I would get a dollar for every windows bug I fix I would be a millionaire by now * return instance _and_ props in runes mode, move flushSync into shared code, don't set accessors in runes mode * goddammit * note breaking change * fix * regenerate messages * Revert "return instance _and_ props in runes mode, move flushSync into shared code, don't set accessors in runes mode" This reverts commit `a47827e57d`. * pass instance to tests --------- Co-authored-by: Simon Holthausen <simon.holthausen@vercel.com>	1 year ago
Rich Harris	94b4268ce3	chore: markdown runtime errors/warnings (#11304 ) * chore: markdown runtime warnings * on second thoughts * start adding errors too * lint * centralise	1 year ago