storefront-api-examples
DISCONTINUED
gatsby-starter-shopify
Our great sponsors
- Appwrite - The open-source backend cloud platform
- InfluxDB - Collect and Analyze Billions of Data Points in Real Time
- Onboard AI - Learn any GitHub repo in 59 seconds
| storefront-api-examples | gatsby-starter-shopify | |
|---|---|---|
| 4 | 9 | |
| 1,091 | 297 | |
| - | -0.3% | |
| 0.0 | 0.0 | |
| 12 days ago | 12 months ago | |
| JavaScript | JavaScript | |
| MIT License | BSD Zero Clause License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
storefront-api-examples
-
Best Practice In GraphQL Queries
Hi, I'm just wondering, it seems that in the storefront-api-examples they use babel-plugin-graphql-js-client-transform to transform GraphQL queries into the format from js-buy-sdk (as far as I understand), but what's wrong with fetch('https://SHOP_NAME.myshopify.com/api/2021-07/graphql.json', {...}), is this somehow deprecated?
gatsby-starter-shopify
-
Is switching to Gatsby front-end for Shopify worth it? How is the dev support and integration? Can you still use Shopify apps?
Are you referring to the payment processing being done at a Shopify's domain instead of the original one? Like how on this gatsby-shopify-demo when clicking checkout it's redirected to https://gatsby-dev-30k-sku.myshopify.com/56348803256/checkouts/....?
Its worth because its easy to develop in and its blazingly fast but you might hit a lot of roadblocks that you'll need to engineer around. We used https://github.com/gatsbyjs/gatsby-starter-shopify and then customized because it gives you a pretty straight forward idea of how to arch a headless app against shopify's api's.
-
E-Commerce Stack Suggestions
I absolutely love Gatsby, but more so for marketing sites. When it comes to Ecommerce, Gatsby developed a Shopify starter: https://github.com/gatsbyjs/gatsby-starter-shopify
-
Gatsby + Shopify: Can you do collection page filtering? Or would Next.js be a better choice?
If you feel like using Gatsby instead, the other store I linked can be forked from here.
What are some alternatives?
js-buy-sdk - The JS Buy SDK is a lightweight library that allows you to build ecommerce into any website. It is based on Shopify's API and provides the ability to retrieve products and collections from your shop, add products to a cart, and checkout.
next-shopify-starter - Nextjs + Tailwind CSS + Shopify Starter
strapi-shopify - 🚀 Integrate Strapi and Shopify
stack-underflow-mern-gql - Feature-rich ‘stack overflow’ (QnA site) clone. Made using MERN + GraphQL stack.
gatsby-plugin-apollo-client - 📡Inject a Shopify Apollo Client into the browser.
apollo-upload-client - A terminating Apollo Link for Apollo Client that fetches a GraphQL multipart request if the GraphQL variables contain files (by default FileList, File, or Blob instances), or else fetches a regular GraphQL POST or GET request (depending on the config and GraphQL operation).
Shopify-api-node - Node Shopify connector sponsored by MONEI
shopify-theme-lab - Shopify theme development environment using Liquid, Vue and Tailwind CSS. Built on top of Shopify CLI 🧪
commerce - Next.js Commerce
Quell - Quell is an easy-to-use, lightweight JavaScript library providing a client- and server-side caching solution for GraphQL. Use Quell to prevent redundant client-side API requests and to minimize costly server-side response latency.
shopify-packer - Modern development tool for Shopify using Webpack 5. Easy to extend and customize, zero build config, compatible with Slate and existing websites.