Don’t publish server in NPM

[osdiab]

Just publish the data model. Server doesn’t need to be npm installable

I’d also rather have that than to have a separate repo for the data model, which would work and be more modular perhaps but would make api development annoying It's kinda nice having them all in the same repo since type errors appear as soon as you change things in a breaking way across the server and client, but that would probably be the most straightforward way to achieve this.

Maybe we can achieve this by making this a monorepo instead of one NPM project—that should work fine.

[osdiab]

cc @rahulgi I think monorepo/workspaces can work fine for this, we had a problem with monorepo with react-native since native doesn't support symlinks and monorepos depend on that. But this is isolated from react-native so it should be fine

[rahulgi]

@osdiab this is fixed, yeah?