Reproduction:

• Run a client with persistent storage, get it in sync with the server
• Take the client offline
• Perform a delete (remotely from a different connected client)
• Take the client back online, the deletion does not sync to the client

Just jotting down some ideas here, am happy to edit this issue to refine/exclude anything you think shouldn't be in scope for this project.

• Import data from file via the console (csv/json etc)
• Import via cli
• Add seed files in whatever format to a folder on the machine hosting the server, on startup the server applies those transactions if they are new (ala the many tools available for RDMS systems)

Reproduction:

• Create a collection on remote with a kebab-case name
• Run triplit migrate pull
• Codegen fails

This appears to be a general issue that keys need to be wrapped in strings before prettifying them in the codegen process

Example: The inferred type of 'schema' cannot be named without a reference to '../node_modules/@triplit/db/dist/types/data-types/boolean'. This is likely not portable. A type annotation is necessary.

Currently the query builder will overwrite values if the same method is used twice. For example client.query('todos').where(['completed', '=', true]).where('author', '=', 'alice') will just include the second where clause. An api like this could be preferred to many filter tuples in a single where statement, and also lets you define a base query with a filter in a variable then append to the where clause later.

There are some complicated edits you could make to a query's filters if the filter is deep and complex (ie deep ands / ors), so we'd need to figure out if/how the api would handle that.

I'm running into a few problems trying to use triplit with react native. One is that after installing triplit, i see this anytime i install:

code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/react
npm ERR!   react@"^18.3.1" from the root project
npm ERR!   peer react@"^16.8.0 || ^17.0.0 || ^18.0.0" from @ahooksjs/[email protected]
npm ERR!   node_modules/@ahooksjs/use-url-state
npm ERR!     @ahooksjs/use-url-state@"^3.5.1" from @triplit/[email protected]
npm ERR!     node_modules/@triplit/console
npm ERR!       @triplit/console@"^0.3.44" from @triplit/[email protected]
npm ERR!       node_modules/@triplit/cli
npm ERR!         dev @triplit/cli@"^0.3.47" from the root project
npm ERR!   33 more (@emotion/react, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"18.2.0" from [email protected]
npm ERR! node_modules/react-native
npm ERR!   react-native@"0.72.6" from the root project
npm ERR!   peer react-native@"^0.0.0-0 || 0.60 - 0.72 || 1000.0.0" from @react-native-async-storage/[email protected]
npm ERR!   node_modules/@react-native-async-storage/async-storage
npm ERR!   11 more (@react-native-community/checkbox, ...)
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/react
npm ERR!   peer react@"18.2.0" from [email protected]
npm ERR!   node_modules/react-native
npm ERR!     react-native@"0.72.6" from the root project
npm ERR!     peer react-native@"^0.0.0-0 || 0.60 - 0.72 || 1000.0.0" from @react-native-async-storage/[email protected]
npm ERR!     node_modules/@react-native-async-storage/async-storage
npm ERR!     11 more (@react-native-community/checkbox, ...)
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /Users/tanishqkancharla/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/tanishqkancharla/.npm/_logs/2024-04-28T23_11_58_027Z-debug-0.log

something about peer dependencies.

When you run triplit dev your database server starts. Although the storage option is available to specify more persistent storage (like sqlite) it is not the default, instead the database will start with en empty in-memory storage instance.

Because the db starts empty, your migrations aren't tracked on the remote database and that can cause some small issues or features to not run (like authz).

From a pure ux perspective its tough to remember to run these migrations and I have to switch to a different terminal window to run them.

Suggestions:

• Run your local migrations when starting the triplit dev server
• When dev runs, if there are unapplied migrations, suggest that i run them
• larger refactor surrounding how schemas/migrations are applied in local development

Moving discussion of RN specific support from this issue to here.

Hi! Thanks for the awesome libraries/database! I'm having a strange issue with Triplit's synchronization, however: when I set up 2 clients and 1 server, it won't work at all. I'll try to provide a more minimal way to reproduce, but it basically is:

• I set up my client application at localhost:5173, and also expose it to local network (make it reachable through 192.168.x.y:5173)
• I set up the development server at localhost:8080, and also expose it to local network (make it reachable through 192.168.x.y:8080)
• On my desktop, I visit my client application at localhost:5173, and set the server's URL to localhost:8080
• On my mobile phone, I visit my client application at 192.168.x.y:5173, and set the server's URL to 192.168.x.y:8080

The synchronization won't work at all between the desktop application and the mobile phone application: I let both connect to the server, but they won't have the same data.

What do you think? Thanks again!

When using the IndexedDbStorage provider it appears a dependency to 'idb' is missing

import { IndexedDbStorage } from "@triplit/db/storage/indexed-db";
import { TriplitClient } from "@triplit/client";
const client = new TriplitClient({
  db: {
    storage: {
      client: new IndexedDbStorage("tripchat-client"),
      outbox: new IndexedDbStorage("tripchat-outbox"),
    }
  }
});

At runtime:
ERROR: Could not resolve "idb/with-async-ittr"

Currently we only detect npm, yarn, and pnpm so when installing with Bun it prompts to manually install the dependencies.

Certain APIs dont have easily accessible query builders. They dont really use a lot of state, so we could export them to make them accessible. Or add a query api to RemoteClient and other utilities without query building capabilities.

Can you add projects that more closely match triplit - for eg. full stack, auto sync, offline support, db schemas, etc.

Here's a short list:

• https://pouchdb.com
• https://feathersjs.com
• https://rethinkdb.com
• https://rxdb.info

Example:

const client = new RemoteClient({ schema });
const result = await client.fetch({
    collectionName: 'todos',
});

// Result is Map<string, any>

I think we need to properly type the query parameter of fetch (so we can pull out the schema and proper return type) or ensure that happens under the hood of fetch somewhere.

Although I can hook into the connection state, I don't have much information as to WHY a client cannot connect.

For example, I may have a malformed connection token, but have no way to pull this specific error information out of the client or react packages.

Without providing this, the app can really only inform the user the app is disconnected, but not what it could do about it (or if it expects that it may be able to reconnect).

Hi folks! I'm trying to setup the chat example locally on my machine. I followed all the steps in the README, including making a github app and filling in the details in .env. On running the app, I get this warning in my console:

And in the triplit terminal, I see this:

Because of which (I think) I'm not seeing any syncing across browsers. Do you folks have any pointers for how I can get this working? Thank you!

It seems based on how we initialize queries when connecting, we may miss updates based on filters.

Reproduction:

• Set up a subscription to a query with a filter on client A and client B
• Add some data
• Take client B offline, mutate data on client A so it is evicted from the query result
• Bring client B back online, see query result does not contain updates

require exports field in package.json points to non existent directory

Fetching relationships with a single cardinality (RelationshipOne / RelationshipById) fails:

TypeError: val.entries is not a function
    at Object.convertJSToJSON (file:///Users/willernst/dev/aspen/next-auth/node_modules/.pnpm/@[email protected][email protected]/node_modules/@triplit/db/dist/data-types/query.js:23:35)

Feel free to close this issue if this is documented somewhere and I missed it. I like the idea here but I found nothing about android support. Is the idea that if you want mobile app support that you should use react native? That's not an option for me but it would be very nice to have some sort of integration with Compose / modern android primitives.

Hi. I'm trying to use query.order, but it seems like it is case-sensitive (A... comes before a...). Is there anyway to make the query case-insensitive (a... and A... are treated the same, but they come before b...)? Thanks!

Hi! Awesome stuff. I've been pulling my hairs solving local-first. How are you guys seamlessly making this look easy. Any limitations encountered so far? What conflicts can Triplit not handle?

In any case... It would be great to have a Solid adapter for this.
How much work would it take to port an adapter for SolidJS? (If it's not super difficult, I'd love to give it a shot)

I think we just need to specify the return type instead of inferring it. We should probably add type tests for the client as well.