shopify-packer VS gatsby-starter-shopify

Shopify Packer written by Eric Hayes is probably the best thing happened to Shopify theme development since Shopify stopped supporting Slate. It's everything we all hoped for and that's a promise. Packer uses Webpack 5 with zero config to compile, bundle, split and minify your modern development technologies and start a server for development with hot module reloading actually working perfectly. It can also create, list and manipulate (delete, download, deploy etc) themes from your shop which is a lifesaver sometimes. I also love using Eric's Shopify Packer because it uses SCSS, Stylelint, ESLint, Babel and PostCSS. It can analyze bundles and have multiple entry points for templates and layouts. It's actually a CLI tool that’s installed globally and you can start a new project or integrate Packer with an existing theme in ridiculously little time. Most importantly you can easily customize all settings for the site and webpack if needed. Eric also provides quick support for the packer so i would highly recommend it and also buy him a beer because he deserves one for this!

GitHub source

Link to your store Follow these instructions here to link your Shopify store. Create a .env file with your Shopify store URL, password, and Storefront access token, using the .env.example file as an example. If you want to try with a development store, see the sample data and instructions here.

Would you say gatsby-shopify-starter is generally a good place to start wirh Gatsby & Shopify?

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/....?

Update: I actually realised that I didn't have nginx-proxy container running! However I'm still having issues accessing pages that are served via SSR.. i.e. '/search', when running 'gatsby serve' behind the nginx reverse proxy. I just get a 404. I can access '/search' when running locally (on port 9000) but not when it's dockerized. I'm aware it may be the case that SSR in Gatsby refers to service rendering purely to produce a build but when I build and deploy the static assets to be served under nginx '/search' still produces a 404. In a nutshell '/search' doesn't work unless being accessed by 'gatsby serve' with no reverse proxy. I've been voicing my troubles on this GitHub ticket: https://github.com/gatsbyjs/gatsby-starter-shopify/issues/57

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

If you feel like using Gatsby instead, the other store I linked can be forked from here.

My budget for now is around 1000-1100$. Because this project is without design and styling, and because there is a huge Gatsby Shopify Starter I think a lot of work has already been done.