mizulu

no error in bun 1.2.16 on windows with the repro

confirmed bug on **linux** docker with `oven/bun:latest` image ``` Bun version: 1.2.16 Platform: linux Architecture: x64 ``` @SinnySupernova you can currently bypass the limit using URL.createObjectURL until this is fixed

https://playground.solidjs.com/anonymous/0392c578-9678-474a-b500-e2d31f64ad70 but this over renders

@deluksic this how it is compiled: ```js return _$createComponent(MyComponent, { get count() { return _$memo(() => !!(console.log("checked"), count() > 0))() ? Infinity : (console.log("accessed"), count()); } }); ``` every time...

Yes the optimization is aimed at JSX / rendering See **"&& intrusive boolean casting memo"** https://github.com/solidjs/solid/discussions/2471 discussion this discussion was more about `&&` but applicable for ternary operator / conditional...

so you are concerned about the fetch on the client side when you trigger the event but have you noticed that you are getting double fetch on the server? even...

@ryansolid > it is more that the event has nothing to do with the data fetching. It fetches once on the server and then it is supposed to use that...

in regard to the original issue, shouldn't a triggered event, while hydrating cause a refetch only if the event would have actually propagated to an element inside the suspense?

@Mrcavas 👍 if solid had a hook for before hydration `onBeforeHydration`, then you can remove the event from the `window.document._$DX_DELEGATE` and restore it when hydration is completed I believe the...

@Mrcavas for my suggestion to work, we need to find a way to transform the registration of the delegated events before the client calls it, `_$delegateEvents(["mousemove"]);` then there shouldn't be...