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

@contentful-tools/store

v0.7.3

Published

An auto-synchronizing in-memory store for Contentful content

Downloads

16

Readme

Contentful Store

Version License Dependencies Dev Dependencies Dependabot Status

npm install @contentful-tools/store

Use in conjunction with: Contentful Tools CLI (npm)

The store caches content in-memory, and can be accessed synchronously in microseconds. It can be set up to synchronize whenever content is accessed, throttled to a configurable minimum interval. This uses the sync endpoint of the Contentful Content Delivery API, which returns the entries and assets that have been added and deleted since the last sync — to efficiently keep content always up-to-date.

Your content can be linked however you like, even circularly. Assets and entries are stored by ID, and links are transparently resolved on the fly, using getter properties. This meshes nicely with a GraphQL API, and allows blazingly fast queries of arbitrary depth. Fields resolve to the value for the requested locale first, but use the base locale’s value as a fallback.

Note, the first fetch after a period of no requests will potentially return stale content, since the store synchronously responds before triggering the sync. If your server is under any appreciable load however, this won’t be a problem. You are at least guaranteed to get back content in a consistent state — you’ll never get partially-synced content.

Also note, this probably won’t work very well in serverless environments, unless you’re doing something to keep your function containers alive between invocations. Otherwise, there’s a fairly high startup cost to pay in order to run the initial sync with Contentful (of course, dependent on the size of your content space).