Aaron Boodman

Treat transaction args as opaque data

5

Currently transaction arguments are decoded in both repc and replicache-sdk-js in various locations. This is both expensive and also prevents us from easily doing useful sanity checks.

We need to correctly implement IDBStore onversionchange

3

Currently it is difficult to use the `drop` API correctly in Replicache. Users must ensure that all connections to the same named replicache instance (across all tabs!) first close their...

We should probably move away from JSON for our values.

5

https://twitter.com/sayrer/status/1301973647267999745 Now that repc is almost done, it's easier for me to see the criticism that has frequently been given that we are unnecessarily coupled to JSON. I think that...

I'm not 100% sure, but it seems like this is showing up in the profile. There's no need for us to copy this data ... the only reason we do...

That tends to be the name we use to refer to it in practice.

Repo: - Create two windows to same room - Create shape in one - Move that shape around in other - Switch focus back to first window - cmd+z Result:...

https://github.com/steveruizok/perfect-cursors was inspired by the `smoothie` library in here, but looks like it might be a little better. For example, every so often smoothie has weird artifacts where cursors animate...

I temporarily disabled it because WriteTransactionImpl doesn't yet support scan().

chore: specify types needed directly.

2

I'm not sure getting them through v10 of Replicache was doing the right thing. When I install replicache-react and replicache v12 together in an app, I only see one version...