3 ms·
So I checked out the git branch for Next.js Commerce (https://github.com/vercel/commerce/ https://github.com/vercel/commerce/). Aside from the missing documenta
by drchiu 6y ago
So I checked out the git branch for Next.js Commerce (https://github.com/vercel/commerce/ https://github.com/vercel/commerce/). Aside from the missing documentation, there seems to be a lot of touch points where the code is tightly integrated with BigCommerce's npm library.
At this point, it does not feel like the headless ecommerce part swappable. I'm sure that with time, the team will probably extract this out so that it's more plug and play (https://github.com/vercel/commerce/issues/2 https://github.com/vercel/commerce/issues/2) or will require the libraries (ie. for Shopify, etc) to follow a certain pattern.
If anyone on the Next.js Commerce team is reading this, the other thing I noticed is that this requires a BigCommerce account. Would be great to have a functionality where one could test out all the end points without needing a third party service in local development. I happen to have a sandbox BigCommerce shop, but there's quite a few steps to get one set up.
- okbel 6y agoAbsolutely. Thanks for the feedback, drchiu. I'm @okbel, actively working on Next.js Commerce. Right now the codebase is tightly coupled with BigCommerce, but in the near future (following days) we plan to add multiple data providers. I'm about to edit docs/bigcommerce.md to clearify usage. Thank you!
- s_severus 6y agoHi @okbel, nice work so far! This project could be huge, and hit the target that vue storefront/deity/others have not quite cracked yet. I'm working on a node/typescript/graphql headless commerce framework (vendure.io) and I'd love to help on an integration if at all possible. Pros of integrating with vendure: users can stand up a fully-functional local server in 1 npx command; no SaaS account needed; low friction for JS devs used to npm work flows & idioms.