npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@cosva-lab/apollo-link-offline

v1.0.2

Published

Offline plug-in for Apollo

Downloads

5

Readme

@cosva-lab/apollo-link-offline

An Apollo Link to queue mutations when offline or network errors exist.

Biggest different between this module and other offline modules available is that this module assumes the worst. It assumes the request will not reach the server and queues all mutations, responds with optimistic response and removes the mutation from the queue when the server responds success.

Reason for this assumption is twofold:

Speed, since all mutations have optimistic response, the UI feels much snappier (like a local app) In cases where the the network is NOT offline but really slow (think 2G in a third world country) and the request doesn't reach the server anyway, our queue retries until the server responds with success.

Usage

Import and initialize this link in just two lines:

import { ApolloLink } from 'apollo-link';
import { createHttpLink, OfflineAction } from '@cosva-lab/apollo-link-offline';
import localforage from 'localforage';


const syncUserCreated: OfflineAction<Pick<
  Mutation,
  'createUser'
>> = ({ cache, optimisticResponse }, newData) => {
  // Read this https://www.apollographql.com/docs/react/caching/cache-interaction/#writequery-and-writefragment
};

const offlineLink = new OfflineLink({
  storage: localforage,
  actions: { syncUserCreated },
});

const link = ApolloLink.from([
  offlineLink,
  ...
]);


export const client = new ApolloClient({
  link,
  cache,
  ...
});

@offline annotation to mutations

apollo-link-offline needs to receive the onSync entry in the @offline annotation to know what function to call when the data is synchronized

Example: @offline (onSync: syncUserCreated)

import gql from 'graphql-tag';

export const CREATE_USER = gql`
  mutation($name: String!) @offline(onSync: syncUserCreated) {
    ...
  }
`;