11 Commits

Author SHA1 Message Date
Lee Robinson
7f8f9ff1a3 use cache 2025-02-09 11:38:22 -06:00
Lee Robinson
887d437795
Prepare for using PPR (#1236) 2024-04-17 21:54:09 -05:00
Lee Robinson
25ddc5e643
Update dependencies. (#1314) 2024-03-26 16:15:01 -05:00
Lee Robinson
1f47796529
Improves form submissions and updates dependencies (#1209) 2023-10-10 21:45:55 -05:00
Michael Novotny
469cd7bffd
Fixes sort by hover (#1146) 2023-08-04 10:59:12 -05:00
Kai Hao
049d903a5b
Removes unnecessary useEffect's on search sorts (#1124) 2023-07-28 11:19:13 -05:00
Lee Robinson
59fc2bc2e9
Update to new design. (#1103) 2023-07-24 19:40:29 -07: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
Stephanie Dietz
acb4ff400b
Updates recommended products to use ProductGridItems component (#975) 2023-04-20 11:27:18 -05: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