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

@dadoagency/gatsby-plugin-aa-builder-checkout

v1.1.9

Published

Query product data from builder.io and the checkout API

Downloads

5

Readme

This plugin is used to source product data from builder.io and the checkout API.

How To publish:

npm publish --access=public

How this works:

On build:

  1. query all the funnel pages that exist
  2. query the product selector for each funnel
  3. get the list of references to ProductVariant
  4. fetch product data from the checkout API for each ProductVariant
  5. merge the checkout API data with the builder data to generate a FunnelPageData node with the following shape:
{
    id: "",
    path: "",
    productSelector: {
        onetime: {
            products: [],
            discounts: []
        },
        subscription: {
            products: [],
            discounts: []
        }
    }
}

The funnel page template should have a single page query that queries funnelPageData where path = '$path' to get all the product data for that specific funnel.

We aren't querying allBuilderModels since they don't include refs so instead we query our own data type 'funnelPageData'

Improvement opportunities:

  • use gatsby cache to cache requests in gatsby-node.js to improve build times
  • create graphql fragments to simplify page queries
  • create a distinction between otp and subs products in builder.io
  • do a single request to the checkout API in sourceNodes per page rather than a request per product (checkoutSDK can query a list of products)