Connecting a Client

To connect your client to the server, you must pass it sync configuration.

import { ClientDescriptor, ServerSync } from './client/index.js';
import migrations from './migrations.js';

const clientDesc = new ClientDescriptor({
    namespace: 'todos',
    migrations,
    sync: {
        initialPresence: {
            emoji: '',
        },
        defaultProfile: { name: '' },
        authEndpoint: 'http://localhost:3000/auth/sync',
    },
});

clientDesc.open().then((todos) => {
    // now we have a todo data client, "todos"
});

You may also define typing for presence data:

export interface Presence {
    emoji: string;
}

export interface Profile {
    // any data you may have put in profiles on the server
}

const clientDesc = new ClientDescriptor<Presence, Profile>({
    // ...
});

To start syncing, call client.sync.start (where client is your instance of Client, i.e. todos above) This will connect to your websocket server. It's up to you to add any authentication and authorization to reject unregistered or unsubscribed clients if you want to limit access to sync. Verdant itself will sync whoever you let connect.

If you want to pause sync, call client.sync.stop (where client is your instance of Client, i.e. todos above).

Custom auth fetch

By default the client will make a basic fetch to your auth endpoint with credentials: 'include'. If this endpoint is hosted on a server which your client already has a cookie session with, it should work out of the box.

If you use another solution for sessions, like a JWT in a header, you can pass in fetchAuth instead of authEndpoint to the sync configuration. This function must return a promise for the JSON response body of the authorization endpoint.