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 🙏

© 2026 – Pkg Stats / Ryan Hefner

apollo-fragment-list-link

v4.0.3

Published

'Read all available fragments from apollo-inmemory-cache'

Readme

apollo-fragment-list-link

Link to Read your all local fragments with Apollo Client!

Apollo Client cache is your single source of truth that holds all of your local data alongside your remote data. But in case of parameterized queries apollo-cache-inmemory it usually very difficult to retrieve client-side data due to stringify key approach in the cache. So apollo-fragment-list-link is the link to read all your client-side fragments with the help of apollo-link-state's @client directive. It can be used as afterware of apollo-http-link, It will find all updated fragments and will put them in the cache with customizable cache key. apollo has introduced @connection directive, with help of it, you can control the key of caching, but in case of a different query containing different filtering parameters, it will be very difficult to read all local fragments which we have already fetched. Suppose we have implemented suggestions query, and have already fetched suggestions with some prefix token, Now we want to read all suggestions offline from the cache,

Suppose we have implemented suggestions query, and have already fetched suggestions with some prefix token, Now we want to read all suggestions offline from the cache,

query fetchSuggestion($token: String!) {
  suggestions(condition:{$startWith:$token}) {
      ...SuggestionItem
  }
}
fragment SuggestionItem on Suggestion {
  id
  name
  label
}

First query variables:

{"token": "Exa"}

Second query variables:

{"token": "To"}

After queries listed above, partial cache status will be

Before

(without apollo-fragment-list-link)

{
    $ROOT_QUERY.fetchSuggestion.(token:"Exa"): [...],
    $ROOT_QUERY.fetchSuggestion.(token:"To"): [...],
  	Suggestion:1,
  	Suggestion:2,
	....
}

After

(with apollo-fragment-list-link)

{
	$ROOT_QUERY.allSuggestions: {
	  totalCount
      nodes: [
       	{id: "Suggestion:1"},
        {id: "Suggestion:2"},
        ...
      ]
	},
    $ROOT_QUERY.fetchSuggestion.(token:"Exa"): [...],
    $ROOT_QUERY.fetchSuggestion.(token:"To"): [...],
  	Suggestion:1,
  	Suggestion:2,
	....
}
const query = gql`
	query clientSuggestions {
		allSuggestions @client {
  			nodes {
  				id
			}
		}
	}
}
`;
const {result} = await client.query({
  query,
})
/*
result = [{id:1,__typename:"Suggestion"}, {id:2,__typename:"Suggestion"}, ...] 
*/

To get started, install apollo-fragment-list-link from npm:

npm install apollo-fragment-list-link --save

Setup

import { withClientState } from 'apollo-link-state';
import ApolloFragmentLink from 'apollo-fragment-list-link';

// This is the same cache you pass into new ApolloClient
const cache = new InMemoryCache(...);
                                
const fragmentLink = new ApolloFragmentLink({
  cache,
  fragmentTypeDefs: [
    gql`
      fragment SuggestionItem on Suggestion {
		id
		name
	  }
    `,
  ],
  // @optional
  createCacheReadKey: ({typename}) => `all${typename}`,
  // @optional 
  createConnectionTypename: ({typename}) => `All${typename}Connection`,
});

const stateLink = withClientState({
  cache,
  resolvers: {
    Query: {
     	...fragmentLink.createStateLinkQueryResolvers()
    },
  }
});

const link = stateLink.concat(fragmentLink.concat(httpLink));

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

Usage

const GET_SUGGESTIONS = gql`
	query clientSuggestions {
		allSuggestions @client {
  			nodes {
  				id
			}
		}
	}
}
`;
const {result} = await client.query({
  query: GET_SUGGESTIONS,
})

Finally, each time you make a change in apollo-link-state, you need to run:

yarn bundle

Now you should be good to go!