Oscar Hermoso

Just found https://github.com/nlopes/actix-web-prom/pull/71 and `exclude_status(actix_http::StatusCode::NOT_FOUND)` I have applied this temporary work around to my repo, but is not in the docs or readme

@hgiesel Consider reopening this? Now that Svelte 4 supports iterators, this could be the syntax for a range expression ``` {#each range(1, 5)} ... {/each} ```

Another workaround, run Playwright in Vitest https://www.the-koi.com/projects/how-to-run-playwright-within-vitest/ This is working well for me

Interesting that reactivity works if you comment out the slot in layout 

Adding this snippet to the bottom of `svelte.config.js` will prevent crashes and help with debugging info during development ```js process.on('unhandledRejection', (reason, promise) => { console.error('Unhandled Rejection at: Promise', promise, 'reason:',...

@Conduitry - Very nice, the `Vary: Accept` header resolves the issue and is definitely a better solution than `'Cache-Control': 'No-Store'`. Perhaps it should be a default response header for routes...

I think it makes perfect sense for the `Vary: Accept` header to be implicitly added where we serve different data on the same URL path. For example, Django REST Framework...

Agree using all of `{#await}`, `{:catch}` and `{:finally}` at the same time would be kind of silly, but this would still be nice to have for scenarios with only `{#await}`...

@KnownRock - Beautiful! I replaced `@aws-sdk/signature-v4` with `@smithy/signature-v4` because the former is deprecated and it worked perfectly. ```diff - import { SignatureV4 } from '@aws-sdk/signature-v4' + import { SignatureV4 }...

If anyone is looking for a short-term workaround, you can crash `air` by sending it a `SIGTERM` with `Ctrl` + `\`