10 Commits

Author SHA1 Message Date
Lee Robinson
7f8f9ff1a3 use cache 2025-02-09 11:38:22 -06:00
Lee Robinson
9a4c995bb6
Make image, variant, and cart updates faster with useOptimistic (#1365) 2024-07-28 22:58:59 -05:00
Michael Novotny
c6eb7a30f9
Changes variants to use router replace (#1157) 2023-08-08 10:00:08 -05:00
Lee Robinson
cd8f4c6b4c
Fix hydration error (#1117)
---------

Co-authored-by: Michael Novotny <manovotny@gmail.com>
2023-07-28 15:00:48 -07:00
Michael Novotny
61b134a66c
Revert "Update variant-selector.tsx (#1115)" (#1116)
This reverts commit 7dc7e6d6e45facc0a7b3ed1816ea123fa6aac84e.
2023-07-25 13:42:51 -07:00
Tim Neutkens
7dc7e6d6e4
Update variant-selector.tsx (#1115) 2023-07-25 13:23:05 -07:00
Michael Novotny
69a68dd408
Fixes Lighthouse accessibility issues (#1112)
Co-authored-by: Lee Robinson <lrobinson2011@gmail.com>
2023-07-25 10:40:39 -07:00
Michael Novotny
29aaa8cac6
Disables link scroll on variant selection (#1109)
* Disables link scroll on variant selection

* Fix TS error
2023-07-25 09:00:31 -07:00
Lee Robinson
59fc2bc2e9
Update to new design. (#1103) 2023-07-24 19:40:29 -07: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