Tal500
Tal500
Alternatively, and maybe it will be simpler, we can just check if the current format is `system` directly in the internal `worker` plugin. If so, then whenever the plugin build...
Implementing the optimization ideas in #618 would probably fix this issue.
> adding `"type": "module",` to package.json seems to indicate that this is a viable fix. although the component did run fine for me even without it. It's a matter of...
> * ComponentConstructorOptions This is a great question - how much let the user the control of the manual hydration, versus the automatic process by Playwright? I think as a...
> Would like to explore the ideas a bit further if you can share a simple repository with SSR use case(s) you want to test? Let's split our discussion to...
Please notice @benmccann that there is a problem with the REPL, I filled up an issue: https://github.com/benmccann/esm-env/issues/1
> I don't think there's anything we can do here. The `page` store only updating after the navigations completes is the correct behavior. To do what you want it's probably...
> @Tal500 @dummdidumm My solution for this was to simply use the `afterNavigate()` lifecycle hook: > > ```svelte > // +layout.svelte > > > import { afterNavigate } from '$app/navigation'...
We can take it a step further and say that the `data` will be a function returning a promise, meaning that if the shared load function doesn't call it, the...
> I don't follow how this is a blocker for #7213 or #7175 (or #7119)? This is a "blocker" using a hack I was hinting in the description: You can...