🦋 Changeset detected

Latest commit:8d82339

The changes in this PR will be included in the next version bump.

Not sure what this means?Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Preview:https://svelte-dev-git-preview-svelte-16280-svelte.vercel.app/

Playground

pnpm add https://pkg.pr.new/svelte@16280

This is a good solution IMO - it doesn't yet work for$effect.pre though, since that's executed in another part. If I change the reproducible to use$effect.preit still fails

Adding similar logic toprocess_effects and returning an empty array seems to fix it.

Good catch. Rather than making changes toprocess_effects, which will create more merge headaches with theasync branch, I think we should park this until that branch is merged. Adding a failing test in the meantime

I've skipped the$effect.pre for now in the interests of merging — we can revisit it onceasync is in

I was having a problem similar to#16072 and after pulling the latest update, it's still there. It happens only if there is an$inspect in the components inside anif directive.

I wasn't able to reproduce exactly that scenario, but I got another issue when trying to recreate it, which also is running code before theif directive executes. Here's asimple REPL, where when you click the button, it assigns undefined to activeTab, which should make the child component disappear, but some code is still running within theif directive, attempting to read from activeTab, and it throws an error (If you remove the$inspect inside the child, the error goes away):

As for my original problem, all I can provide are these screenshots since I couldn't reproduce, but this is just for reference, the REPL above is enough to trigger the issue:

Here's the error:

And here's where that error is thrown, which as you can see, that code shouldn't even be running given the condition of theif statement.:

@abtinturing please create a new issue.