David Fahlander

dexie-cloud-addon cannot be used with [email protected] but needs 4.x: ``` npm i dexie@next ```

Could it be that you've already created the db with table "todos" using ++id as primary key. Try rename or delete the db. Same error? Also what error do you...

Seems the addons are not active. It could be the unnamed imports that doesnt do their job in the webpack setup (just a theory). Try explicitly provide the addons to...

The new sample still does the same type of import as before: ```js import 'dexie-observable'; import 'dexie-syncable'; ``` Try if naming the default imports helps: ```js import observable from 'dexie-observable';...

Ok, then we'll have to check why dexie-observable doesn't respect the $$ prefix. Until solved, try generating an UUID manually. There's a helper function for that in [Dexie.Observable.createUUID()](http://dexie.org/docs/Observable/Dexie.Observable#dexieobservablecreateuuid)

The public realm does not need any invites. Any user is implicitely member of it with readonly access.

Interesting. I don't think that use case was anticipated when implementing it, but it would probably make sense to support it and apply all changes

Typings are missing for Dexie.debug but it will respect it in regards of console logging. dexie-cloud-addon does not yet respect this value but a new version coming out soon will...

Thanks! This kind of error should be validated earlier in Table.get() to prohibit this kind of native error happening deep within dexie. The async call stack doesn't reveal much. Would...

Thanks @nlaurie ! Do you have a link to a repository where we will find it?