io

Turns out this was the erroneous behavior I was happening upon: https://github.com/facebook/react/pull/26256

We're also experiencing this issue on 13.1.5 with `pages/` (not `app/`)

Another clue for this happening with `/pages` too (still in `13.1.6`) is that we are using suspense in that universe (via `@tanstack/query`)

Turns out my problem, which I think is in fact separate from this one, was caused in my project by using `react@next` (`18.3.0-next-0f4a83596-20230110` to be precise). Returning to `[email protected]` has...

Turns out this was the erroneous behavior I was happening upon: https://github.com/facebook/react/pull/26256

This changed the undocumented way to programmatically preload `LoadableComponent`s from `dynamic`, it is now `LoadableComponent.preload()` rather than `LoadableComponent.render.preload()`.

@arishoham as described the method is still there except it is now on the parent rather than `render`

> As of Next 13.1 it appears that preload method doesn't exist as described above. It doesn't even appear to be an object. > > Is there a known fix?...

@agusterodin did you try calling/logging `Timeline.preload` yet? You can use `console.dir` to see any properties of a function instead of the stringified function as `console.log`provides

Piling on: We're batching analytics events to dispatch with `sendBeacon` [on `blur`/`hidden`/`pagehide`/`beforeunload`](https://github.com/tjek/tjek-js-sdk/blob/develop/lib/kits/events/tracker.ts#L283), and we're having mixed luck testing this with [`page.close({ runBeforeUnload: true })`](https://github.com/tjek/tjek-js-sdk/blob/develop/__tests__/chrome/events_kit.test-chrome.ts#L81) or hacks like https://github.com/microsoft/playwright/issues/2286#issuecomment-1442368623