They are breaking only for experimental features.

The current (soon to be old) method would be creating a +server endpoint and then fetching it. The future (currently experimental) method would be a command remote function.

svelte.dev/docs/kit/rou...

svelte.dev/docs/kit/rem...

I’m also curious. There are some cases where it seems unavoidable, like setting a Tween value based on an incoming prop.

This is great! Can’t wait to dive in.

With server unit tests, do you ever have issues with the client side form or others not lining up with the server side? I tend to prefer playwright integration tests to test the whole flow, but it is slower and more difficult to mock the db.

Hi, cool project! I was testing out and the svelte reactivity doesn't seem to be working: svelte.dev/playground/8...

Same. I’ve used tanstack query in the react world quite a lot, but haven’t felt like I needed it in sveltekit. Using it just for mutations seems interesting.

Are you using tanstack query for page data loading too? Curious to see an example of the code you came up with to do this.

Is the phone app able to see it? My limited understanding is it is just a device on your network, so if something else can see it then that at least confirms that the light is staying connected. Could be a setting with the control center app having access to the local network if so.

What was the benefit of Astro over sveltekit? I’d expect pre-rendered page in sveltekit to be comparable.