
Product
Introducing Webhook Events for Alert Changes
Add real-time Socket webhook events to your workflows to automatically receive software supply chain alert changes in real time.
@graphql-live/client
Advanced tools
âš WARNING: Still under development.
Very tiny library to send live queries to a compatible GraphQL server (@graphql-live/server) using the @live directive and automatically get updates when fresh data is available. Under the hood, the client uses Socket.IO to communicate and receives JSON patches to perform surgical updates of previous results (side note : you don't have to think about it), thus optimizing bandwidth usage.
Of course, it also supports standard queries and mutations (subscriptions might come in the futur).
yarn add @graphql-live/client
There are two ways to use this library :
You first have to create a client :
import { createClient } from "@graphql-live/client";
const client = createClient({
url: "http://localhost:8080"
});
This establishes a socket connection with the server at the given url. You can then execute (and subscribe to) a GraphQL operation using the Observable pattern by calling client.execute :
const operation = {
operation: `
query($id: ID!) @live {
getUser(id: $id) {
id
name
job
}
}
`,
variables: {
id: "8dd870"
}
};
// Option 1, by hand :
const observable = {
subscribe: observer => ({
unsubscribe: client.execute(operation, observer)
})
};
// Option 2, with RxJS (could be another library as long as it implements the Observable pattern) :
const observable = Rx.Observable.create(observer =>
client.execute(operation, observer)
);
// Then subscribe to results (this also sends the operation to the server) :
const subscription = observable.subscribe({
next: result => doSomethingWith(result),
complete: () => doAnotherThing()
});
// ...Finally, when you're no more interested in updates :
subscription.unsubscribe();
(Take note of the @live directive)
Most GraphQL client libraries support add-on systems (Apollo's links, urql's exchanges, etc.). Currently, @graphql-live/client ships with two such add-ons :
LiveLink for Apollo :
import { ApolloClient, InMemoryCache } from "@apollo/client";
import { LiveLink } from "@graphql-live/client/dist/apollo";
const client = new ApolloClient({
cache: new InMemoryCache(),
link: new LiveLink({
url: "http://localhost:8080"
})
});
liveExchange for urql :
import { createClient, dedupExchange } from "urql";
import { cacheExchange } from "@urql/exchange-graphcache";
import { liveExchange } from "@graphql-live/client/dist/urql";
const client = createClient({
url: "http://localhost:8080",
exchanges: [
dedupExchange,
cacheExchange(),
liveExchange({
url: "http://localhost:8080"
})
]
});
You can add a custom context callback to your client config. It will be called right before an operation is sent to the server and it's return value can be used server-side to generate custom resolver context. This might typically be used to pass auth tokens, but really it could be any valid JSON.
const client = createClient({
url: "http://localhost:8080",
context() {
return auth().currentUser.token;
}
});
Note: createClient, LiveLink and liveExchange all accept the same options.
You can pass any valid Socket.IO client options to the live query client, including a custom path :
const client = createClient({
url: "http://localhost:8080",
socketOptions: {
path: "/api"
}
});
createClientdeclare function createClient<TContext = any>(
options?: ClientOptions<TContext>
): {
socket: Socket;
destroy: () => void;
execute: (operation: Operation, observer: ResultObserver) => () => void;
};
When you create a client, what you actually get back is an object containing the active socket, a destroy callback to release all listeners and disconnect the socket, and the execute function seen above.
LiveLinkdeclare class LiveLink<TContext = any> extends ApolloLink {
constructor(options?: ClientOptions<TContext>);
}
liveExchangedeclare function liveExchange<TContext = any>(
options?: ClientOptions<TContext>
): Exchange;
type ClientOptions<TContext = any> = {
url?: string;
socketOptions?: Partial<ManagerOptions & SocketOptions>;
context?(payload: ContextPayload): TContext | Promise<TContext>;
};
type ContextPayload = {
socket: Socket;
operation: Operation;
};
type ResultObserver = {
next?(value: ExecutionResult): void;
error?(error: any): void;
complete?(): void;
};
type Operation = {
operation: string;
operationName?: string | null;
variables?: Record<string, any>;
};
FAQs
The client part of the GraphQLive package
We found that @graphql-live/client demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Product
Add real-time Socket webhook events to your workflows to automatically receive software supply chain alert changes in real time.

Security News
ENISA has become a CVE Program Root, giving the EU a central authority for coordinating vulnerability reporting, disclosure, and cross-border response.

Product
Socket now scans OpenVSX extensions, giving teams early detection of risky behaviors, hidden capabilities, and supply chain threats in developer tools.