Sam Willis

First, I think there is going to be two ways people want to do SSR with `useShape`: 1. Fetch the full snapshot on the server, render it, and then include...

A little more information on why we need to chunk these responses: The linearlite demo has two tables, issues (~80mb) and comments (~250mb). It seems the browser really doesn't like...

I've cherry picked out all the changes to PGlite + the sync plugin, they are now all in main with docs and testing, and most were released (just windowed live...

@balegas could I get you to review the merge logic: https://github.com/electric-sql/pglite/pull/393/files#diff-9ea8511284754ad34fc4d8ee4bf19aeb0996d57e0b22ac29589580fe7e21848a @msfstef if you have a moment early next week could you have a skim though the app code. Versions...

This example was moved into the main Electric monorepo

In the video below: 1. Start electric 2. Load an initial batch of 10 issues + comments into Postgres 3. Start the front end which creates the shapes 4. Stop...

This crash is due to the size of the transaction loading the data. The script to load the data was doing it in a single transaction, splitting it into batches...

> However, when existing clients have received a response from a live request, there's no problem with caching it for longer. > They're not going to go back, they're going...

I would expect that to work. Is the PGliteWorker instance working in your setup without going via Drizzle?

Hey, thanks for looking into this, I've posters over on the Deno issue, I'm very keen to make this happen. One thing I am aware of if that the Emscripten...