
Research
/Security News
60 Malicious Ruby Gems Used in Targeted Credential Theft Campaign
A RubyGems malware campaign used 60 malicious packages posing as automation tools to steal credentials from social media and marketing tool users.
gatsby-source-shopify
Advanced tools
Gatsby source plugin for building websites using Shopfiy as a data source.
Source plugin for pulling data into Gatsby from Shopify stores via the Shopify Storefront API.
gatsby-transformer-sharp
and gatsby-image
for product and
article imagesnpm install --save gatsby-source-shopify
// In your gatsby-config.js
plugins: [
/*
* Gatsby's data processing layer begins with “source”
* plugins. Here the site sources its data from Shopify.
*/
{
resolve: "gatsby-source-shopify",
options: {
// The domain name of your Shopify shop. This is required.
// Example: 'gatsby-source-shopify-test-shop' if your Shopify address is
// 'gatsby-source-shopify-test-shop.myshopify.com'.
shopName: "gatsby-source-shopify-test-shop",
// An API access token to your Shopify shop. This is required.
// You can generate an access token in the "Manage private apps" section
// of your shop's Apps settings. In the Storefront API section, be sure
// to select "Allow this app to access your storefront data using the
// Storefront API".
// See: https://help.shopify.com/api/custom-storefronts/storefront-api/getting-started#authentication
accessToken: "example-wou7evoh0eexuf6chooz2jai2qui9pae4tieph1sei4deiboj",
// Set verbose to true to display a verbose output on `npm run develop`
// or `npm run build`. This prints which nodes are being fetched and how
// much time was required to fetch and process the data.
// Defaults to true.
verbose: true,
},
},
]
You can query nodes created from Shopify using GraphQL like the following:
Note: Learn to use the GraphQL tool and Ctrl+Spacebar at http://localhost:8000/___graphql to discover the types and properties of your GraphQL model.
{
allShopifyProduct {
edges {
node {
id
title
handle
productType
vendor
variants {
id
title
price
}
}
}
}
}
All Shopify data is pulled using the Shopify Storefront API. Data is made available in the same structure as provided by the API, with a few exceptions noted below.
The following data types are available:
Name | Description |
---|---|
Article | A blog entry. |
Blog | Collection of articles. |
Comment | A comment on a blog entry. |
Collection | Represents a grouping of products that a shop owner can create to organize them or make their shops easier to browse. |
Product | Represents an individual item for sale in a Shopify store. |
ProductOption | Custom product property names. |
ProductVariant | Represents a different version of a product, such as differing sizes or differing colors. |
ProductType | Represents a category of products. |
ShopPolicy | Policy that a merchant has configured for their store, such as their refund or privacy policy. |
For each data type listed above, shopify${typeName}
and
allShopify${typeName}
is made available. Nodes that are closely related, such
as Article
and Comment
, are provided as node fields as described below.
Note: The following examples are not a complete reference to the available fields for each node. Utilize Gatsby's built-in GraphQL tool to discover the types and properties available.
The associated blog data is provided on the blog
field. Article comments are
provided on the comments
field.
{
allShopifyArticle {
edges {
node {
id
author {
email
name
}
blog {
title
}
comments {
id
author {
email
name
}
contentHtml
}
contentHtml
publishedAt(formatString: "ddd, MMMM Do, YYYY")
}
}
}
}
Blog data is provided on the blog
field on Article
, but it can be queried
directly like the following:
{
allShopifyBlog {
edges {
node {
id
title
url
}
}
}
}
Comments are provided on the comments
field on Article
, but they can be
queried directly like the following:
{
allShopifyComment {
edges {
node {
id
author {
email
name
}
contentHtml
}
}
}
}
Products in the collection are provided on the products
field.
{
allShopifyCollection {
edges {
node {
id
descriptionHtml
handle
image {
src
alt
}
products {
id
handle
title
}
title
}
}
}
}
Product variants and options are provided on the variants
and options
fields.
{
allShopifyProduct {
edges {
node {
id
descriptionHtml
handle
images {
originalSrc
}
variants {
id
availableForSale
image {
originalSrc
}
price
selectedOptions {
name
value
}
sku
title
}
title
}
}
}
}
Product options are provided on the options
field on Product
, but they can
be queried directly like the following:
{
allShopifyProductOption {
edges {
node {
id
name
values
}
}
}
}
Product variants are provided on the variants
field on Product
, but they
can be queried directly like the following:
{
allShopifyProductVariant {
edges {
node {
id
availableForSale
image {
originalSrc
}
price
selectedOptions {
name
value
}
sku
title
}
}
}
}
Shop policies include the following types:
privacyPolicy
)refundPolicy
)termsOfService
)The type of policy is provided on the type
field. Policies can be queried
like the following:
{
allShopifyShopPolicy {
edges {
node {
body
title
type
}
}
}
}
To use image processing you need gatsby-transformer-sharp
,
gatsby-plugin-sharp
, and their dependencies gatsby-image
and
gatsby-source-filesystem
in your gatsby-config.js
.
You can apply image processing to any image field on a node. Image processing of inline images added to description fields is currently not supported.
To access image processing in your queries, you need to use this pattern, where
...ImageFragment
is one of the gatsby-transformer-sharp
fragments:
{
allShopifyProduct {
edges {
node {
id
images {
localFile {
childImageSharp {
...ImageFragment
}
}
}
}
}
}
}
Full example:
{
allShopifyProduct {
edges {
node {
id
images {
localFile {
childImageSharp {
resolutions(width: 500, height: 300) {
...GatsbyImageSharpResolutions_withWebp
}
}
}
}
}
}
}
}
To learn more about image processing, check the documentation of gatsby-plugin-sharp.
gatsby-node.js
exampleconst path = require("path")
exports.createPages = async ({ graphql, boundActionCreators }) => {
const { createPage } = boundActionCreators
const pages = await graphql(`
{
allShopifyProduct {
edges {
node {
id
handle
}
}
}
}
`)
pages.data.allShopifyProduct.edges.forEach(edge => {
createPage({
path: `/${edge.node.handle}`,
component: path.resolve("./src/templates/product.js"),
context: {
id: edge.node.id,
},
})
})
}
Not all Shopify nodes have been implemented as they are not necessary for the
static portion of a Gatsby-generated website. This includes any node that
contains sensitive customer-specific information, such as Order
and
Payment
.
If you are in need of this data (e.g. building a private, internal website), please open an issue. Until then, the nodes will not be implemented to lessen the chances of someone accidentally making private information publicly available.
FAQs
Gatsby source plugin for building websites using Shopify as a data source.
The npm package gatsby-source-shopify receives a total of 2,991 weekly downloads. As such, gatsby-source-shopify popularity was classified as popular.
We found that gatsby-source-shopify demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 7 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
/Security News
A RubyGems malware campaign used 60 malicious packages posing as automation tools to steal credentials from social media and marketing tool users.
Security News
The CNA Scorecard ranks CVE issuers by data completeness, revealing major gaps in patch info and software identifiers across thousands of vulnerabilities.
Research
/Security News
Two npm packages masquerading as WhatsApp developer libraries include a kill switch that deletes all files if the phone number isn’t whitelisted.