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

gatsby-source-salsify

v1.1.0

Published

Fetch data from Salsify API

Downloads

6

Readme

gatsby-source-salsify

A Gatsby plugin for using Salsify as a data source.

Install

npm install --save gatsby-source-salsify

or with Yarn:

yarn add gatsby-source-salsify

How to use

// In your gatsby-config.js
plugins: [
	{
		resolve: 'gatsby-source-salsify',
		options: {
			ids: ['U2508', 'U2000'],
			apiKey: "your_salsify_key",
			org: "your_salsify_org_id",
			concurrency: 10, // Number of simultaneous fetches to salsify (default = 10)
		},
	},
]

Or use markdown files that contain an "id" property in front matter to determine which products to use:

// In your gatsby-config.js
plugins: [
	{
		resolve: 'gatsby-source-salsify',
		options: {
			markdownPath: `${__dirname}/src/markdown/products`,
			apiKey: "your_salsify_key",
			org: "your_salsify_org_id",
		},
	},
]

apiKey is optional if your key is an environment variable. If it is not supplied in the options, it will still try to look for the key in the environment variable process.env.SALSIFY_API_KEY.

Configuration

Types

Salsify's API likes to interchange arrays for strings if there's only one item in the array. To make this more reliable, you can specify arrays with the types option.

options: {
	types: {
		myList: 'array'
	}
}

Media

Salsify's API won't automatically pass along media objects. To specify which properties are supposed to return media objects (which include the URL), use the media option.

options: {
	media: [
		'myImages',
		'videos',
	]
}

How to query

Note: All properties will be converted to camelcase so they play nice with GraphQL.

{
	salsifyContent(id: { eq: $id }){
		itemName
	}
}