Amir Arad

Hi I think it would be very beneficial to be able to get an in-memory DB in the browser that is 100% compatible with the backend's DB. It can be...

@endel sure thing. I'm just documenting what I find. been helping @a-rts write a mobx client, and found this edge, so it's yours to decide what to do with it.

shouldn't it "Just work"(TM)? I mean, the API for a property decorator is compatible with the API for accessor decorator. https://www.typescriptlang.org/docs/handbook/decorators.html

@endel funny you mention it, I wrote [the original mobx proxy draft](https://github.com/mobxjs/mobx/pull/776)

@naive17 I'm having similar problems after switching the frontend bundler to use esbuild while the backend still uses typescript. could you tell us about your build stack? (my very wild...

yeah, vite uses esbuild. I [switched to `esbuild-loader` myself and stayed in webpack](https://github.com/starwards/starwards/commit/1dcfdb7cb74d231e0b6f6b74ae27f78e2f3a12ba), so it sounds like the same problem more or less. I'm going to try to pre-bundle the...

For future reference, pre-bundling the common code worked for me: It prevented the browser bundler from re-arranging the schema files, thus kept the loading order in sync between server and...

@naive17 I suspect there is some kind of concurrency race condition in your build job? so that sometimes the same order is kept between client and server, and sometimes not?

module's master branch may be broken at time of test. if possible, should install the release tag.

@TarVK what should replace the mixing approach?