4
0
forked from crowetic/commerce

11 Commits

Author SHA1 Message Date
Michael Novotny
8c8240956a
Removes Framer Motion (#1055) 2023-06-21 15:13:58 -07:00
Logan
7eb8816854
Fixed misaligned navbar links (#1048) 2023-06-16 13:50:10 -05:00
Lee Robinson
fecc60eb36
Update dependencies and fix TS errors. (#1041) 2023-06-06 20:36:44 -05:00
Michael Novotny
f5dade74fb
Fixes search page bugs. (#1019) 2023-05-12 16:02:51 -07:00
Michael Novotny
a0c0d10fae
Changes mobile menu animation to be consistent with cart animation. (#1015) 2023-05-11 12:53:04 -07:00
Tobias Lins
9ea5671579
Don't fail when collections are not found (#996)
* Don't fail when collections are not found

* fix another error
2023-04-26 09:26:52 -05:00
Michael Novotny
7de3ae5583
Removes unnecessary async on ProductGridItems (#977) 2023-04-20 13:54:04 -05:00
Stephanie Dietz
acb4ff400b
Updates recommended products to use ProductGridItems component (#975) 2023-04-20 11:27:18 -05:00
Stephanie Dietz
a677c17f78
Update canary version to fix scroll to top. (#976) 2023-04-20 10:40:29 -05:00
Michael Novotny
67a192eba8
Adds documentation on how to configure Next.js Commerce and Shopify (#974) 2023-04-20 06:46:35 -04:00
Lee Robinson
fd9450aecb
Next.js Commerce refresh. (#966)
We're making some updates to Next.js Commerce. Everything prior to this commit marks what we're calling [`v1`](https://github.com/vercel/commerce/releases/tag/v1) as a point in time to be able to reference and still use going into the future. The current architecture of Commerce is a multi-vendor, interoperable solution, including:

- [Shopify](https://shopify.vercel.store/)
- [Swell](https://swell.vercel.store/)
- [BigCommerce](https://bigcommerce.vercel.store/)
- [Vendure](https://vendure.vercel.store/)
- [Saleor](https://saleor.vercel.store/)
- [Ordercloud](https://ordercloud.vercel.store/)
- [Spree](https://spree.vercel.store/)
- [Kibo Commerce](https://kibocommerce.vercel.store/)
- [Commerce.js](https://commercejs.vercel.store/)
- [SalesForce Cloud Commerce](https://salesforce-cloud-commerce.vercel.store/)

All features can be toggled on or off, and it's easy to change between commerce providers. To support this, we needed to create a ["commerce metaframework"](d1d9e8c434/packages/commerce/new-provider.md) where providers could confirm to an API spec to add support for Next.js Commerce. While this worked and was successful for `v1`, we have different design goals and ambitions for `v2`.

**What You Need To Know**

- `v1` will not be updated moving forward. If you need to reference `v1`, you will still be able to clone and deploy the version tagged at this release.
- `v2` will be shifting to be a single provider vs. provider agnostic. Other providers are welcome to fork this repository and swap out the underlying `lib/` implementation that connects to the selected commerce provider (Shopify). This architecture was chosen to reduce the surface area of the codebase, remove the intermediate metaframework layer for provider-interoperability, and enable usage with the latest Next.js and React features.
- We will be sharing more about `v2` in the future as we continue to iterate before the marked release.
2023-04-17 22:00:47 -05:00