Sam Willis

PGlite maintainer here, let me know if there is anything you need if you decide to do this. Happy to help out.

Unfortunately it seems that esbuild doesn't follow the pattern that other bundlers have settled on interpreting `new URL('./relative/path/to/file', import.meta.url)` as a way to find files to bundle, then rewrite that...

The alternative is an explicit .start() method on a shape stream. It solves two issues: - allowing multiple or lazy subscribing to a stream (passing it to a Shape) -...

Initial reaction to builder concept was a -1, but it actually translates really nicely to a builder pattern for client side processing of the streams - so I'm a +1...

@msfstef agreed, in general I prefer a declarative api. Thinking about it further, we don't need the implied "deep run", but not that the output of the join include won't...

@KyleAMathews note that we could add multiple subscribe calls *at intermediate steps* in a shape query: ```ts const comments = new ShapeStreamBuilder() .setUrl(url) .setShapeDefinition(shapeDef) .query() // we don't need to...

I think materialise may be a separate import too, we are likely to have multiple implementations: in-memory, SQLite, PGlite, any other persistence. We would then also likely have a .toStream()...

@msfstef whether we end up with the pipe api, or something similar, it will be a separate lib/import, and internally subscribe. As the underlying fetch is async, if multiple subscribes...

Hey @sebastorama Sorry for being slow to get back to you, latter half of December + early January are always a little busy... Did you try doing a `VACUUM FULL`?...

Hey @SemStassen That seems confusing, its essentially identical code to in Linearlite 🤔 First thing to try is disabling React strict mode, let's just double check that it's not causing...