commerce/pnpm-lock.yaml

1247 lines
41 KiB
YAML
Raw Permalink Normal View History

2024-07-24 14:05:34 -05:00
lockfileVersion: '9.0'
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"](https://github.com/vercel/commerce/blob/d1d9e8c4343e70d72df6e00ec95f6ea4efbb7c54/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 23:00:47 -04:00
2023-10-27 14:11:18 -05:00
settings:
autoInstallPeers: true
excludeLinksFromLockfile: false
2024-10-15 22:07:55 -05:00
importers:
2024-12-06 08:23:35 -06:00
2024-07-24 14:05:34 -05:00
.:
dependencies:
'@headlessui/react':
2024-12-06 08:23:35 -06:00
specifier: ^2.2.0
version: 2.2.0(react-dom@19.0.0(react@19.0.0))(react@19.0.0)
2024-07-24 14:05:34 -05:00
'@heroicons/react':
2024-12-06 08:23:35 -06:00
specifier: ^2.2.0
version: 2.2.0(react@19.0.0)
2024-07-24 14:05:34 -05:00
clsx:
specifier: ^2.1.1
version: 2.1.1
geist:
specifier: ^1.3.1
2025-02-21 12:39:31 -06:00
version: 1.3.1(next@15.2.0-canary.67(react-dom@19.0.0(react@19.0.0))(react@19.0.0))
2024-07-24 14:05:34 -05:00
next:
2025-02-21 12:39:31 -06:00
specifier: 15.2.0-canary.67
version: 15.2.0-canary.67(react-dom@19.0.0(react@19.0.0))(react@19.0.0)
2024-07-24 14:05:34 -05:00
react:
2024-12-06 08:23:35 -06:00
specifier: 19.0.0
version: 19.0.0
2024-07-24 14:05:34 -05:00
react-dom:
2024-12-06 08:23:35 -06:00
specifier: 19.0.0
version: 19.0.0(react@19.0.0)
sonner:
2025-02-21 12:39:31 -06:00
specifier: ^2.0.1
version: 2.0.1(react-dom@19.0.0(react@19.0.0))(react@19.0.0)
2024-07-24 14:05:34 -05:00
devDependencies:
'@tailwindcss/container-queries':
specifier: ^0.1.1
2025-02-21 12:39:31 -06:00
version: 0.1.1(tailwindcss@4.0.8)
2025-02-09 11:38:22 -06:00
'@tailwindcss/postcss':
2025-02-21 12:39:31 -06:00
specifier: ^4.0.8
version: 4.0.8
2024-07-24 14:05:34 -05:00
'@tailwindcss/typography':
2025-02-09 11:38:22 -06:00
specifier: ^0.5.16
2025-02-21 12:39:31 -06:00
version: 0.5.16(tailwindcss@4.0.8)
2024-07-24 14:05:34 -05:00
'@types/node':
2025-02-21 12:39:31 -06:00
specifier: 22.13.4
version: 22.13.4
2024-07-24 14:05:34 -05:00
'@types/react':
2025-02-21 12:39:31 -06:00
specifier: 19.0.10
version: 19.0.10
2024-07-24 14:05:34 -05:00
'@types/react-dom':
2025-02-21 12:39:31 -06:00
specifier: 19.0.4
version: 19.0.4(@types/react@19.0.10)
2024-07-24 14:05:34 -05:00
postcss:
2025-02-21 12:39:31 -06:00
specifier: ^8.5.3
version: 8.5.3
2024-07-24 14:05:34 -05:00
prettier:
2025-02-21 12:39:31 -06:00
specifier: 3.5.1
version: 3.5.1
2024-07-24 14:05:34 -05:00
prettier-plugin-tailwindcss:
2025-02-09 11:38:22 -06:00
specifier: ^0.6.11
2025-02-21 12:39:31 -06:00
version: 0.6.11(prettier@3.5.1)
2024-07-24 14:05:34 -05:00
tailwindcss:
2025-02-21 12:39:31 -06:00
specifier: ^4.0.8
version: 4.0.8
2024-07-24 14:05:34 -05:00
typescript:
2025-02-09 11:38:22 -06:00
specifier: 5.7.3
version: 5.7.3
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"](https://github.com/vercel/commerce/blob/d1d9e8c4343e70d72df6e00ec95f6ea4efbb7c54/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 23:00:47 -04:00
packages:
2024-12-06 08:23:35 -06:00
2024-07-24 14:05:34 -05:00
'@alloc/quick-lru@5.2.0':
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-UrcABB+4bUrFABwbluTIBErXwvbsU/V7TZWfmbgJfbkwiBuziS9gxdODUyuiecfdGQ85jglMW6juS3+z5TsKLw==}
engines: {node: '>=10'}
'@emnapi/runtime@1.3.1':
resolution: {integrity: sha512-kEBmG8KyqtxJZv+ygbEim+KCGtIq1fC22Ms3S4ziXmYKm8uyoLX0MHONVKwp+9opg390VaKRNt4a7A9NwmpNhw==}
2025-02-09 11:38:22 -06:00
'@floating-ui/core@1.6.9':
resolution: {integrity: sha512-uMXCuQ3BItDUbAMhIXw7UPXRfAlOAvZzdK9BWpE60MCn+Svt3aLn9jsPTi/WNGlRUu2uI0v5S7JiIUsbsvh3fw==}
2024-12-06 08:23:35 -06:00
2025-02-09 11:38:22 -06:00
'@floating-ui/dom@1.6.13':
resolution: {integrity: sha512-umqzocjDgNRGTuO7Q8CU32dkHkECqI8ZdMZ5Swb6QAM0t5rnlrN3lGo1hdpscRd3WS8T6DKYK4ephgIH9iRh3w==}
2024-12-06 08:23:35 -06:00
'@floating-ui/react-dom@2.1.2':
resolution: {integrity: sha512-06okr5cgPzMNBy+Ycse2A6udMi4bqwW/zgBF/rwjcNqWkyr82Mcg8b0vjX8OJpZFy/FKjJmw6wV7t44kK6kW7A==}
2024-07-24 14:05:34 -05:00
peerDependencies:
react: '>=16.8.0'
react-dom: '>=16.8.0'
2024-12-06 08:23:35 -06:00
'@floating-ui/react@0.26.28':
resolution: {integrity: sha512-yORQuuAtVpiRjpMhdc0wJj06b9JFjrYF4qp96j++v2NBpbi6SEGF7donUJ3TMieerQ6qVkAv1tgr7L4r5roTqw==}
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"](https://github.com/vercel/commerce/blob/d1d9e8c4343e70d72df6e00ec95f6ea4efbb7c54/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 23:00:47 -04:00
peerDependencies:
2024-07-24 14:05:34 -05:00
react: '>=16.8.0'
react-dom: '>=16.8.0'
2025-02-09 11:38:22 -06:00
'@floating-ui/utils@0.2.9':
resolution: {integrity: sha512-MDWhGtE+eHw5JW7lq4qhc5yRLS11ERl1c7Z6Xd0a58DozHES6EnNNwUWbMiG4J9Cgj053Bhk8zvlhFYKVhULwg==}
2024-12-06 08:23:35 -06:00
'@headlessui/react@2.2.0':
resolution: {integrity: sha512-RzCEg+LXsuI7mHiSomsu/gBJSjpupm6A1qIZ5sWjd7JhARNlMiSA4kKfJpCKwU9tE+zMRterhhrP74PvfJrpXQ==}
engines: {node: '>=10'}
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"](https://github.com/vercel/commerce/blob/d1d9e8c4343e70d72df6e00ec95f6ea4efbb7c54/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 23:00:47 -04:00
peerDependencies:
2024-12-06 08:23:35 -06:00
react: ^18 || ^19 || ^19.0.0-rc
react-dom: ^18 || ^19 || ^19.0.0-rc
'@heroicons/react@2.2.0':
resolution: {integrity: sha512-LMcepvRaS9LYHJGsF0zzmgKCUim/X3N/DQKc4jepAXJ7l8QxJ1PmxJzqplF2Z3FE4PqBAIGyJAQ/w4B5dsqbtQ==}
2023-07-24 21:40:29 -05:00
peerDependencies:
2024-12-06 08:23:35 -06:00
react: '>= 16 || ^19.0.0-rc'
2024-10-15 22:07:55 -05:00
'@img/sharp-darwin-arm64@0.33.5':
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-UT4p+iz/2H4twwAoLCqfA9UH5pI6DggwKEGuaPy7nCVQ8ZsiY5PIcrRvD1DzuY3qYL07NtIQcWnBSY/heikIFQ==}
engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
2024-08-13 13:33:05 -05:00
cpu: [arm64]
os: [darwin]
2024-10-15 22:07:55 -05:00
'@img/sharp-darwin-x64@0.33.5':
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-fyHac4jIc1ANYGRDxtiqelIbdWkIuQaI84Mv45KvGRRxSAa7o7d1ZKAOBaYbnepLC1WqxfpimdeWfvqqSGwR2Q==}
engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
2024-08-13 13:33:05 -05:00
cpu: [x64]
os: [darwin]
2024-10-15 22:07:55 -05:00
'@img/sharp-libvips-darwin-arm64@1.0.4':
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-XblONe153h0O2zuFfTAbQYAX2JhYmDHeWikp1LM9Hul9gVPjFY427k6dFEcOL72O01QxQsWi761svJ/ev9xEDg==}
2024-08-13 13:33:05 -05:00
cpu: [arm64]
os: [darwin]
2024-10-15 22:07:55 -05:00
'@img/sharp-libvips-darwin-x64@1.0.4':
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-xnGR8YuZYfJGmWPvmlunFaWJsb9T/AO2ykoP3Fz/0X5XV2aoYBPkX6xqCQvUTKKiLddarLaxpzNe+b1hjeWHAQ==}
2024-08-13 13:33:05 -05:00
cpu: [x64]
os: [darwin]
2024-10-15 22:07:55 -05:00
'@img/sharp-libvips-linux-arm64@1.0.4':
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-9B+taZ8DlyyqzZQnoeIvDVR/2F4EbMepXMc/NdVbkzsJbzkUjhXv/70GQJ7tdLA4YJgNP25zukcxpX2/SueNrA==}
2024-08-13 13:33:05 -05:00
cpu: [arm64]
os: [linux]
2024-10-15 22:07:55 -05:00
'@img/sharp-libvips-linux-arm@1.0.5':
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-gvcC4ACAOPRNATg/ov8/MnbxFDJqf/pDePbBnuBDcjsI8PssmjoKMAz4LtLaVi+OnSb5FK/yIOamqDwGmXW32g==}
2024-08-13 13:33:05 -05:00
cpu: [arm]
os: [linux]
2024-10-15 22:07:55 -05:00
'@img/sharp-libvips-linux-s390x@1.0.4':
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-u7Wz6ntiSSgGSGcjZ55im6uvTrOxSIS8/dgoVMoiGE9I6JAfU50yH5BoDlYA1tcuGS7g/QNtetJnxA6QEsCVTA==}
2024-08-13 13:33:05 -05:00
cpu: [s390x]
os: [linux]
2024-10-15 22:07:55 -05:00
'@img/sharp-libvips-linux-x64@1.0.4':
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-MmWmQ3iPFZr0Iev+BAgVMb3ZyC4KeFc3jFxnNbEPas60e1cIfevbtuyf9nDGIzOaW9PdnDciJm+wFFaTlj5xYw==}
2024-08-13 13:33:05 -05:00
cpu: [x64]
os: [linux]
2024-10-15 22:07:55 -05:00
'@img/sharp-libvips-linuxmusl-arm64@1.0.4':
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-9Ti+BbTYDcsbp4wfYib8Ctm1ilkugkA/uscUn6UXK1ldpC1JjiXbLfFZtRlBhjPZ5o1NCLiDbg8fhUPKStHoTA==}
2024-08-13 13:33:05 -05:00
cpu: [arm64]
os: [linux]
2024-10-15 22:07:55 -05:00
'@img/sharp-libvips-linuxmusl-x64@1.0.4':
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-viYN1KX9m+/hGkJtvYYp+CCLgnJXwiQB39damAO7WMdKWlIhmYTfHjwSbQeUK/20vY154mwezd9HflVFM1wVSw==}
2024-08-13 13:33:05 -05:00
cpu: [x64]
os: [linux]
2024-10-15 22:07:55 -05:00
'@img/sharp-linux-arm64@0.33.5':
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-JMVv+AMRyGOHtO1RFBiJy/MBsgz0x4AWrT6QoEVVTyh1E39TrCUpTRI7mx9VksGX4awWASxqCYLCV4wBZHAYxA==}
engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
2024-08-13 13:33:05 -05:00
cpu: [arm64]
os: [linux]
2024-10-15 22:07:55 -05:00
'@img/sharp-linux-arm@0.33.5':
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-JTS1eldqZbJxjvKaAkxhZmBqPRGmxgu+qFKSInv8moZ2AmT5Yib3EQ1c6gp493HvrvV8QgdOXdyaIBrhvFhBMQ==}
engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
2024-08-13 13:33:05 -05:00
cpu: [arm]
os: [linux]
2024-10-15 22:07:55 -05:00
'@img/sharp-linux-s390x@0.33.5':
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-y/5PCd+mP4CA/sPDKl2961b+C9d+vPAveS33s6Z3zfASk2j5upL6fXVPZi7ztePZ5CuH+1kW8JtvxgbuXHRa4Q==}
engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
2024-08-13 13:33:05 -05:00
cpu: [s390x]
os: [linux]
2024-10-15 22:07:55 -05:00
'@img/sharp-linux-x64@0.33.5':
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-opC+Ok5pRNAzuvq1AG0ar+1owsu842/Ab+4qvU879ippJBHvyY5n2mxF1izXqkPYlGuP/M556uh53jRLJmzTWA==}
engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
2024-08-13 13:33:05 -05:00
cpu: [x64]
os: [linux]
2024-10-15 22:07:55 -05:00
'@img/sharp-linuxmusl-arm64@0.33.5':
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-XrHMZwGQGvJg2V/oRSUfSAfjfPxO+4DkiRh6p2AFjLQztWUuY/o8Mq0eMQVIY7HJ1CDQUJlxGGZRw1a5bqmd1g==}
engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
2024-08-13 13:33:05 -05:00
cpu: [arm64]
os: [linux]
2024-10-15 22:07:55 -05:00
'@img/sharp-linuxmusl-x64@0.33.5':
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-WT+d/cgqKkkKySYmqoZ8y3pxx7lx9vVejxW/W4DOFMYVSkErR+w7mf2u8m/y4+xHe7yY9DAXQMWQhpnMuFfScw==}
engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
2024-08-13 13:33:05 -05:00
cpu: [x64]
os: [linux]
2024-10-15 22:07:55 -05:00
'@img/sharp-wasm32@0.33.5':
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-ykUW4LVGaMcU9lu9thv85CbRMAwfeadCJHRsg2GmeRa/cJxsVY9Rbd57JcMxBkKHag5U/x7TSBpScF4U8ElVzg==}
engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
2024-08-13 13:33:05 -05:00
cpu: [wasm32]
2024-10-15 22:07:55 -05:00
'@img/sharp-win32-ia32@0.33.5':
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-T36PblLaTwuVJ/zw/LaH0PdZkRz5rd3SmMHX8GSmR7vtNSP5Z6bQkExdSK7xGWyxLw4sUknBuugTelgw2faBbQ==}
engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
2024-08-13 13:33:05 -05:00
cpu: [ia32]
os: [win32]
2024-10-15 22:07:55 -05:00
'@img/sharp-win32-x64@0.33.5':
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-MpY/o8/8kj+EcnxwvrP4aTJSWw/aZ7JIGR4aBeZkZw5B7/Jn+tY9/VNwtcoGmdT7GfggGIU4kygOMSbYnOrAbg==}
engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
2024-08-13 13:33:05 -05:00
cpu: [x64]
os: [win32]
2025-02-21 12:39:31 -06:00
'@next/env@15.2.0-canary.67':
resolution: {integrity: sha512-Is8AU8GcBrDoyXTmEKPTM+K87Xb5SA545jkw0E6+51Zb/1sg5MSCH9OmQf2KlvbqSrkiVuQ8UA23pY5+xGFGpw==}
2024-12-06 08:23:35 -06:00
2025-02-21 12:39:31 -06:00
'@next/swc-darwin-arm64@15.2.0-canary.67':
resolution: {integrity: sha512-BNBt0qWhnZR2pSxlofSBsmy5PYRa7/t4txnYH5z41lSs0B9OlhlsYyiokefmiw6EKKLxzT23hmb+ZPtxTCjiFw==}
2024-12-06 08:23:35 -06:00
engines: {node: '>= 10'}
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"](https://github.com/vercel/commerce/blob/d1d9e8c4343e70d72df6e00ec95f6ea4efbb7c54/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 23:00:47 -04:00
cpu: [arm64]
os: [darwin]
2025-02-21 12:39:31 -06:00
'@next/swc-darwin-x64@15.2.0-canary.67':
resolution: {integrity: sha512-ZPC0/iL3dhexN+MQ6QOfaOO6y3WMhyxns01KA9mae0V0sp/uC+KwpSbNCVXptjmiZQ9j0Q9TYjqQBQ4KwtBK8Q==}
2024-12-06 08:23:35 -06:00
engines: {node: '>= 10'}
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"](https://github.com/vercel/commerce/blob/d1d9e8c4343e70d72df6e00ec95f6ea4efbb7c54/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 23:00:47 -04:00
cpu: [x64]
os: [darwin]
2025-02-21 12:39:31 -06:00
'@next/swc-linux-arm64-gnu@15.2.0-canary.67':
resolution: {integrity: sha512-t+i9tRB0uYj3OoZS2qhPwDrlcf5bRTKQY5GtFwboyCzBLv9KcU1xa3cwXulNxq1soo8wTiWRnhq8CkvUT+Fbvw==}
2024-12-06 08:23:35 -06:00
engines: {node: '>= 10'}
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"](https://github.com/vercel/commerce/blob/d1d9e8c4343e70d72df6e00ec95f6ea4efbb7c54/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 23:00:47 -04:00
cpu: [arm64]
os: [linux]
2025-02-21 12:39:31 -06:00
'@next/swc-linux-arm64-musl@15.2.0-canary.67':
resolution: {integrity: sha512-9jffwDN4X2ER5eqj16XJHCf4MmRI3QI0L52JLYH9/3OPxD86bDeQlH/+NK3iEu/3X4KX1rDb7cF9uulB9hjfXw==}
2024-12-06 08:23:35 -06:00
engines: {node: '>= 10'}
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"](https://github.com/vercel/commerce/blob/d1d9e8c4343e70d72df6e00ec95f6ea4efbb7c54/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 23:00:47 -04:00
cpu: [arm64]
os: [linux]
2025-02-21 12:39:31 -06:00
'@next/swc-linux-x64-gnu@15.2.0-canary.67':
resolution: {integrity: sha512-pWp5NIAbMLKy6tfZF22tsDC3A9IJm/p+UQf9l906NClYKtMXLYDFmapXVpTUB7fdb9xDOvB+DtAX11nQk5bukw==}
2024-12-06 08:23:35 -06:00
engines: {node: '>= 10'}
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"](https://github.com/vercel/commerce/blob/d1d9e8c4343e70d72df6e00ec95f6ea4efbb7c54/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 23:00:47 -04:00
cpu: [x64]
os: [linux]
2025-02-21 12:39:31 -06:00
'@next/swc-linux-x64-musl@15.2.0-canary.67':
resolution: {integrity: sha512-RjSu9pEgQuUmkt1FINCCvpV0SHYrLpf7LaF7pZPem1N2lgDySnazt4ag7ZDaWL0XMBiTKGmNxkk185HeST2PSg==}
2024-12-06 08:23:35 -06:00
engines: {node: '>= 10'}
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"](https://github.com/vercel/commerce/blob/d1d9e8c4343e70d72df6e00ec95f6ea4efbb7c54/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 23:00:47 -04:00
cpu: [x64]
os: [linux]
2025-02-21 12:39:31 -06:00
'@next/swc-win32-arm64-msvc@15.2.0-canary.67':
resolution: {integrity: sha512-DM+ysK87Q10MkoxgZeFOZsRx4Yt1WtynDVZoogdEjikfxZrMLCEo22O2uFVNh2E0kHCdE89K3dODO9rQz9EjAw==}
2024-12-06 08:23:35 -06:00
engines: {node: '>= 10'}
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"](https://github.com/vercel/commerce/blob/d1d9e8c4343e70d72df6e00ec95f6ea4efbb7c54/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 23:00:47 -04:00
cpu: [arm64]
os: [win32]
2025-02-21 12:39:31 -06:00
'@next/swc-win32-x64-msvc@15.2.0-canary.67':
resolution: {integrity: sha512-gI3Hk/6YrFXMJn018ZjZo832Pxrsj2DpyXbLc9Vxs4wOZ0x3ChVk2yhFA/SJZY7yhdD3vwG9Srdn8gfCuO4xHg==}
2024-12-06 08:23:35 -06:00
engines: {node: '>= 10'}
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"](https://github.com/vercel/commerce/blob/d1d9e8c4343e70d72df6e00ec95f6ea4efbb7c54/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 23:00:47 -04:00
cpu: [x64]
os: [win32]
2025-02-09 11:38:22 -06:00
'@react-aria/focus@3.19.1':
resolution: {integrity: sha512-bix9Bu1Ue7RPcYmjwcjhB14BMu2qzfJ3tMQLqDc9pweJA66nOw8DThy3IfVr8Z7j2PHktOLf9kcbiZpydKHqzg==}
2024-07-24 14:05:34 -05:00
peerDependencies:
2024-12-06 08:23:35 -06:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
2025-02-09 11:38:22 -06:00
react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
2024-07-24 14:05:34 -05:00
2025-02-09 11:38:22 -06:00
'@react-aria/interactions@3.23.0':
resolution: {integrity: sha512-0qR1atBIWrb7FzQ+Tmr3s8uH5mQdyRH78n0krYaG8tng9+u1JlSi8DGRSaC9ezKyNB84m7vHT207xnHXGeJ3Fg==}
2024-07-24 14:05:34 -05:00
peerDependencies:
2024-12-06 08:23:35 -06:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
2025-02-09 11:38:22 -06:00
react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
2024-12-06 08:23:35 -06:00
'@react-aria/ssr@3.9.7':
resolution: {integrity: sha512-GQygZaGlmYjmYM+tiNBA5C6acmiDWF52Nqd40bBp0Znk4M4hP+LTmI0lpI1BuKMw45T8RIhrAsICIfKwZvi2Gg==}
engines: {node: '>= 12'}
2024-07-24 14:05:34 -05:00
peerDependencies:
2024-12-06 08:23:35 -06:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
2024-07-24 14:05:34 -05:00
2025-02-09 11:38:22 -06:00
'@react-aria/utils@3.27.0':
resolution: {integrity: sha512-p681OtApnKOdbeN8ITfnnYqfdHS0z7GE+4l8EXlfLnr70Rp/9xicBO6d2rU+V/B3JujDw2gPWxYKEnEeh0CGCw==}
2024-07-24 14:05:34 -05:00
peerDependencies:
2024-12-06 08:23:35 -06:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
2025-02-09 11:38:22 -06:00
react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
2024-07-24 14:05:34 -05:00
2024-12-06 08:23:35 -06:00
'@react-stately/utils@3.10.5':
resolution: {integrity: sha512-iMQSGcpaecghDIh3mZEpZfoFH3ExBwTtuBEcvZ2XnGzCgQjeYXcMdIUwAfVQLXFTdHUHGF6Gu6/dFrYsCzySBQ==}
2024-07-24 14:05:34 -05:00
peerDependencies:
2024-12-06 08:23:35 -06:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
2024-07-24 14:05:34 -05:00
2025-02-09 11:38:22 -06:00
'@react-types/shared@3.27.0':
resolution: {integrity: sha512-gvznmLhi6JPEf0bsq7SwRYTHAKKq/wcmKqFez9sRdbED+SPMUmK5omfZ6w3EwUFQHbYUa4zPBYedQ7Knv70RMw==}
2024-07-24 14:05:34 -05:00
peerDependencies:
2024-12-06 08:23:35 -06:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0-rc.1
2024-07-24 14:05:34 -05:00
'@swc/counter@0.1.3':
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-e2BR4lsJkkRlKZ/qCHPw9ZaSxc0MVUd7gtbtaB7aMvHeJVYe8sOB8DBZkP2DtISHGSku9sCK6T6cnY0CtXrOCQ==}
2024-10-15 22:07:55 -05:00
2024-12-06 08:23:35 -06:00
'@swc/helpers@0.5.15':
resolution: {integrity: sha512-JQ5TuMi45Owi4/BIMAJBoSQoOJu12oOk/gADqlcUL9JEdHB8vyjUSsxqeNXnmXHjYKMi2WcYtezGEEhqUI/E2g==}
2024-07-24 14:05:34 -05:00
'@tailwindcss/container-queries@0.1.1':
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-p18dswChx6WnTSaJCSGx6lTmrGzNNvm2FtXmiO6AuA1V4U5REyoqwmT6kgAsIMdjo07QdAfYXHJ4hnMtfHzWgA==}
2023-07-24 21:40:29 -05:00
peerDependencies:
tailwindcss: '>=3.2.0'
2025-02-21 12:39:31 -06:00
'@tailwindcss/node@4.0.8':
resolution: {integrity: sha512-FKArQpbrbwv08TNT0k7ejYXpF+R8knZFAatNc0acOxbgeqLzwb86r+P3LGOjIeI3Idqe9CVkZrh4GlsJLJKkkw==}
2025-02-21 12:39:31 -06:00
'@tailwindcss/oxide-android-arm64@4.0.8':
resolution: {integrity: sha512-We7K79+Sm4mwJHk26Yzu/GAj7C7myemm7PeXvpgMxyxO70SSFSL3uCcqFbz9JA5M5UPkrl7N9fkBe/Y0iazqpA==}
2025-02-09 11:38:22 -06:00
engines: {node: '>= 10'}
cpu: [arm64]
os: [android]
2024-12-06 08:23:35 -06:00
2025-02-21 12:39:31 -06:00
'@tailwindcss/oxide-darwin-arm64@4.0.8':
resolution: {integrity: sha512-Lv9Isi2EwkCTG1sRHNDi0uRNN1UGFdEThUAGFrydRmQZnraGLMjN8gahzg2FFnOizDl7LB2TykLUuiw833DSNg==}
2025-02-09 11:38:22 -06:00
engines: {node: '>= 10'}
cpu: [arm64]
os: [darwin]
2024-03-26 16:15:01 -05:00
2025-02-21 12:39:31 -06:00
'@tailwindcss/oxide-darwin-x64@4.0.8':
resolution: {integrity: sha512-fWfywfYIlSWtKoqWTjukTHLWV3ARaBRjXCC2Eo0l6KVpaqGY4c2y8snUjp1xpxUtpqwMvCvFWFaleMoz1Vhzlw==}
2025-02-09 11:38:22 -06:00
engines: {node: '>= 10'}
cpu: [x64]
os: [darwin]
2025-02-21 12:39:31 -06:00
'@tailwindcss/oxide-freebsd-x64@4.0.8':
resolution: {integrity: sha512-SO+dyvjJV9G94bnmq2288Ke0BIdvrbSbvtPLaQdqjqHR83v5L2fWADyFO+1oecHo9Owsk8MxcXh1agGVPIKIqw==}
2025-02-09 11:38:22 -06:00
engines: {node: '>= 10'}
cpu: [x64]
os: [freebsd]
2025-02-21 12:39:31 -06:00
'@tailwindcss/oxide-linux-arm-gnueabihf@4.0.8':
resolution: {integrity: sha512-ZSHggWiEblQNV69V0qUK5vuAtHP+I+S2eGrKGJ5lPgwgJeAd6GjLsVBN+Mqn2SPVfYM3BOpS9jX/zVg9RWQVDQ==}
2025-02-09 11:38:22 -06:00
engines: {node: '>= 10'}
cpu: [arm]
os: [linux]
2024-12-06 08:23:35 -06:00
2025-02-21 12:39:31 -06:00
'@tailwindcss/oxide-linux-arm64-gnu@4.0.8':
resolution: {integrity: sha512-xWpr6M0OZLDNsr7+bQz+3X7zcnDJZJ1N9gtBWCtfhkEtDjjxYEp+Lr5L5nc/yXlL4MyCHnn0uonGVXy3fhxaVA==}
2025-02-09 11:38:22 -06:00
engines: {node: '>= 10'}
cpu: [arm64]
os: [linux]
2025-02-21 12:39:31 -06:00
'@tailwindcss/oxide-linux-arm64-musl@4.0.8':
resolution: {integrity: sha512-5tz2IL7LN58ssGEq7h/staD7pu/izF/KeMWdlJ86WDe2Ah46LF3ET6ZGKTr5eZMrnEA0M9cVFuSPprKRHNgjeg==}
2025-02-09 11:38:22 -06:00
engines: {node: '>= 10'}
cpu: [arm64]
os: [linux]
2024-12-06 08:23:35 -06:00
2025-02-21 12:39:31 -06:00
'@tailwindcss/oxide-linux-x64-gnu@4.0.8':
resolution: {integrity: sha512-KSzMkhyrxAQyY2o194NKVKU9j/c+NFSoMvnHWFaNHKi3P1lb+Vq1UC19tLHrmxSkKapcMMu69D7+G1+FVGNDXQ==}
2025-02-09 11:38:22 -06:00
engines: {node: '>= 10'}
cpu: [x64]
os: [linux]
2025-02-21 12:39:31 -06:00
'@tailwindcss/oxide-linux-x64-musl@4.0.8':
resolution: {integrity: sha512-yFYKG5UtHTRimjtqxUWXBgI4Tc6NJe3USjRIVdlTczpLRxq/SFwgzGl5JbatCxgSRDPBFwRrNPxq+ukfQFGdrw==}
2025-02-09 11:38:22 -06:00
engines: {node: '>= 10'}
cpu: [x64]
os: [linux]
2025-02-21 12:39:31 -06:00
'@tailwindcss/oxide-win32-arm64-msvc@4.0.8':
resolution: {integrity: sha512-tndGujmCSba85cRCnQzXgpA2jx5gXimyspsUYae5jlPyLRG0RjXbDshFKOheVXU4TLflo7FSG8EHCBJ0EHTKdQ==}
2025-02-09 11:38:22 -06:00
engines: {node: '>= 10'}
cpu: [arm64]
os: [win32]
2025-02-21 12:39:31 -06:00
'@tailwindcss/oxide-win32-x64-msvc@4.0.8':
resolution: {integrity: sha512-T77jroAc0p4EHVVgTUiNeFn6Nj3jtD3IeNId2X+0k+N1XxfNipy81BEkYErpKLiOkNhpNFjPee8/ZVas29b2OQ==}
2025-02-09 11:38:22 -06:00
engines: {node: '>= 10'}
cpu: [x64]
os: [win32]
2025-02-21 12:39:31 -06:00
'@tailwindcss/oxide@4.0.8':
resolution: {integrity: sha512-KfMcuAu/Iw+DcV1e8twrFyr2yN8/ZDC/odIGta4wuuJOGkrkHZbvJvRNIbQNhGh7erZTYV6Ie0IeD6WC9Y8Hcw==}
2025-02-09 11:38:22 -06:00
engines: {node: '>= 10'}
2025-02-21 12:39:31 -06:00
'@tailwindcss/postcss@4.0.8':
resolution: {integrity: sha512-SUwlrXjn1ycmUbA0o0n3Y0LqlXqxN5R8HR+ti+OBbRS79wl2seDmiypEs3xJCuQXe07ol81s1AmRMitBmPveJA==}
2024-12-06 08:23:35 -06:00
2025-02-09 11:38:22 -06:00
'@tailwindcss/typography@0.5.16':
resolution: {integrity: sha512-0wDLwCVF5V3x3b1SGXPCDcdsbDHMBe+lkFzBRaHeLvNi+nrrnZ1lA18u+OTWO8iSWU2GxUOCvlXtDuqftc1oiA==}
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"](https://github.com/vercel/commerce/blob/d1d9e8c4343e70d72df6e00ec95f6ea4efbb7c54/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 23:00:47 -04:00
peerDependencies:
2025-02-09 11:38:22 -06:00
tailwindcss: '>=3.0.0 || insiders || >=4.0.0-alpha.20 || >=4.0.0-beta.1'
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"](https://github.com/vercel/commerce/blob/d1d9e8c4343e70d72df6e00ec95f6ea4efbb7c54/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 23:00:47 -04:00
2025-02-09 11:38:22 -06:00
'@tanstack/react-virtual@3.13.0':
resolution: {integrity: sha512-CchF0NlLIowiM2GxtsoKBkXA4uqSnY2KvnXo+kyUFD4a4ll6+J0qzoRsUPMwXV/H26lRsxgJIr/YmjYum2oEjg==}
peerDependencies:
react: ^16.8.0 || ^17.0.0 || ^18.0.0 || ^19.0.0
react-dom: ^16.8.0 || ^17.0.0 || ^18.0.0 || ^19.0.0
2025-02-09 11:38:22 -06:00
'@tanstack/virtual-core@3.13.0':
resolution: {integrity: sha512-NBKJP3OIdmZY3COJdWkSonr50FMVIi+aj5ZJ7hI/DTpEKg2RMfo/KvP8A3B/zOSpMgIe52B5E2yn7rryULzA6g==}
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"](https://github.com/vercel/commerce/blob/d1d9e8c4343e70d72df6e00ec95f6ea4efbb7c54/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 23:00:47 -04:00
2025-02-21 12:39:31 -06:00
'@types/node@22.13.4':
resolution: {integrity: sha512-ywP2X0DYtX3y08eFVx5fNIw7/uIv8hYUKgXoK8oayJlLnKcRfEYCxWMVE1XagUdVtCJlZT1AU4LXEABW+L1Peg==}
2024-03-26 16:15:01 -05:00
2025-02-21 12:39:31 -06:00
'@types/react-dom@19.0.4':
resolution: {integrity: sha512-4fSQ8vWFkg+TGhePfUzVmat3eC14TXYSsiiDSLI0dVLsrm9gZFABjPy/Qu6TKgl1tq1Bu1yDsuQgY3A3DOjCcg==}
2025-02-09 11:38:22 -06:00
peerDependencies:
'@types/react': ^19.0.0
2024-12-06 08:23:35 -06:00
2025-02-21 12:39:31 -06:00
'@types/react@19.0.10':
resolution: {integrity: sha512-JuRQ9KXLEjaUNjTWpzuR231Z2WpIwczOkBEIvbHNCzQefFIT0L8IqE6NV6ULLyC1SI/i234JnDoMkfg+RjQj2g==}
2024-07-24 14:05:34 -05:00
busboy@1.6.0:
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-8SFQbg/0hQ9xy3UNTB0YEnsNBbWfhf7RtnzpL7TkBiTBRfrQ9Fxcnz7VJsleJpyp6rVLvXiuORqjlHi5q+PYuA==}
engines: {node: '>=10.16.0'}
2025-02-21 12:39:31 -06:00
caniuse-lite@1.0.30001700:
resolution: {integrity: sha512-2S6XIXwaE7K7erT8dY+kLQcpa5ms63XlRkMkReXjle+kf6c5g38vyMl+Z5y8dSxOFDhcFe+nxnn261PLxBSQsQ==}
2024-07-24 14:05:34 -05:00
client-only@0.0.1:
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-IV3Ou0jSMzZrd3pZ48nLkT9DA7Ag1pnPzaiQhpW7c3RbcqqzvzzVu+L8gfqMp/8IM2MQtSiqaCxrrcfu8I8rMA==}
2024-07-24 14:05:34 -05:00
clsx@2.1.1:
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-eYm0QWBtUrBWZWG0d386OGAw16Z995PiOVo2B7bjWSbHedGl5e0ZWaq65kOGgUSNesEIDkB9ISbTg/JK9dhCZA==}
engines: {node: '>=6'}
2024-07-24 14:05:34 -05:00
color-convert@2.0.1:
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-RRECPsj7iu/xb5oKYcsFHSppFNnsj/52OVTRKb4zP5onXwVF3zVmmToNcOfGC+CRDpfK/U584fMg38ZHCaElKQ==}
engines: {node: '>=7.0.0'}
2024-07-24 14:05:34 -05:00
color-name@1.1.4:
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-dOy+3AuW3a2wNbZHIuMZpTcgjGuLU/uBL/ubcZF9OXbDo8ff4O8yVp5Bf0efS8uEoYo5q4Fx7dY9OgQGXgAsQA==}
2024-08-13 13:33:05 -05:00
color-string@1.9.1:
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-shrVawQFojnZv6xM40anx4CkoDP+fZsw/ZerEMsW/pyzsRbElpsL/DBVW7q3ExxwusdNXI3lXpuhEZkzs8p5Eg==}
2024-08-13 13:33:05 -05:00
color@4.2.3:
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-1rXeuUUiGGrykh+CeBdu5Ie7OJwinCgQY0bc7GCRxy5xVHy+moaqkpL/jqQq0MtQOeYcrqEz4abc5f0KtU7W4A==}
engines: {node: '>=12.5.0'}
2024-07-24 14:05:34 -05:00
cssesc@3.0.0:
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-/Tb/JcjK111nNScGob5MNtsntNM1aCNUDipB/TkwZFhyDrrE47SOx/18wF2bbjgc3ZzCSKW1T5nt5EbFoAz/Vg==}
engines: {node: '>=4'}
hasBin: true
2022-12-21 17:51:55 +02:00
2024-07-24 14:05:34 -05:00
csstype@3.1.3:
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-M1uQkMl8rQK/szD0LNhtqxIPLpimGm8sOBwU7lLnCpSbTyY3yeU1Vc7l4KT5zT4s/yOxHH5O7tIuuLOCnLADRw==}
2024-08-13 13:33:05 -05:00
2025-02-09 11:38:22 -06:00
detect-libc@1.0.3:
resolution: {integrity: sha512-pGjwhsmsp4kL2RTz08wcOlGN83otlqHeD/Z5T8GXZB+/YcpQ/dgo+lbU8ZsGxV0HIvqqxo9l7mqYwyYMD9bKDg==}
engines: {node: '>=0.10'}
hasBin: true
2024-08-13 13:33:05 -05:00
detect-libc@2.0.3:
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-bwy0MGW55bG41VqxxypOsdSdGqLwXPI/focwgTYCFMbdUiBAxLg9CFzG08sz2aqzknwiX7Hkl0bQENjg8iLByw==}
engines: {node: '>=8'}
2024-03-26 16:15:01 -05:00
2025-02-09 11:38:22 -06:00
enhanced-resolve@5.18.1:
resolution: {integrity: sha512-ZSW3ma5GkcQBIpwZTSRAI8N71Uuwgs93IezB7mf7R60tC8ZbJideoDNKjHn2O9KIlx6rkGTTEk1xUCK2E1Y2Yg==}
engines: {node: '>=10.13.0'}
2024-07-24 14:05:34 -05:00
geist@1.3.1:
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-Q4gC1pBVPN+D579pBaz0TRRnGA4p9UK6elDY/xizXdFk/g4EKR5g0I+4p/Kj6gM0SajDBZ/0FvDV9ey9ud7BWw==}
2024-07-24 14:05:34 -05:00
peerDependencies:
next: '>=13.2.0'
2024-03-26 16:15:01 -05:00
2025-02-09 11:38:22 -06:00
graceful-fs@4.2.11:
resolution: {integrity: sha512-RbJ5/jmFcNNCcDV5o9eTnBLJ/HszWV0P73bc+Ff4nS/rJj+YaS6IGyiOL0VoBYX+l1Wrl3k63h/KrH+nhJ0XvQ==}
2024-08-13 13:33:05 -05:00
is-arrayish@0.3.2:
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-eVRqCvVlZbuw3GrM63ovNSNAeA1K16kaR/LRY/92w0zxQ5/1YzwblUX652i4Xs9RwAGjW9d9y6X88t8OaAJfWQ==}
2024-03-26 16:15:01 -05:00
2025-02-09 11:38:22 -06:00
jiti@2.4.2:
resolution: {integrity: sha512-rg9zJN+G4n2nfJl5MW3BMygZX56zKPNVEYYqq7adpmMh4Jn2QNEwhvQlFy6jPVdcod7txZtKHWnyZiA3a0zP7A==}
hasBin: true
2024-12-06 08:23:35 -06:00
2025-02-09 11:38:22 -06:00
lightningcss-darwin-arm64@1.29.1:
resolution: {integrity: sha512-HtR5XJ5A0lvCqYAoSv2QdZZyoHNttBpa5EP9aNuzBQeKGfbyH5+UipLWvVzpP4Uml5ej4BYs5I9Lco9u1fECqw==}
engines: {node: '>= 12.0.0'}
cpu: [arm64]
os: [darwin]
2025-02-09 11:38:22 -06:00
lightningcss-darwin-x64@1.29.1:
resolution: {integrity: sha512-k33G9IzKUpHy/J/3+9MCO4e+PzaFblsgBjSGlpAaFikeBFm8B/CkO3cKU9oI4g+fjS2KlkLM/Bza9K/aw8wsNA==}
engines: {node: '>= 12.0.0'}
cpu: [x64]
os: [darwin]
2025-02-09 11:38:22 -06:00
lightningcss-freebsd-x64@1.29.1:
resolution: {integrity: sha512-0SUW22fv/8kln2LnIdOCmSuXnxgxVC276W5KLTwoehiO0hxkacBxjHOL5EtHD8BAXg2BvuhsJPmVMasvby3LiQ==}
engines: {node: '>= 12.0.0'}
cpu: [x64]
os: [freebsd]
2025-02-09 11:38:22 -06:00
lightningcss-linux-arm-gnueabihf@1.29.1:
resolution: {integrity: sha512-sD32pFvlR0kDlqsOZmYqH/68SqUMPNj+0pucGxToXZi4XZgZmqeX/NkxNKCPsswAXU3UeYgDSpGhu05eAufjDg==}
engines: {node: '>= 12.0.0'}
cpu: [arm]
os: [linux]
2025-02-09 11:38:22 -06:00
lightningcss-linux-arm64-gnu@1.29.1:
resolution: {integrity: sha512-0+vClRIZ6mmJl/dxGuRsE197o1HDEeeRk6nzycSy2GofC2JsY4ifCRnvUWf/CUBQmlrvMzt6SMQNMSEu22csWQ==}
engines: {node: '>= 12.0.0'}
cpu: [arm64]
os: [linux]
2025-02-09 11:38:22 -06:00
lightningcss-linux-arm64-musl@1.29.1:
resolution: {integrity: sha512-UKMFrG4rL/uHNgelBsDwJcBqVpzNJbzsKkbI3Ja5fg00sgQnHw/VrzUTEc4jhZ+AN2BvQYz/tkHu4vt1kLuJyw==}
engines: {node: '>= 12.0.0'}
cpu: [arm64]
os: [linux]
2025-02-09 11:38:22 -06:00
lightningcss-linux-x64-gnu@1.29.1:
resolution: {integrity: sha512-u1S+xdODy/eEtjADqirA774y3jLcm8RPtYztwReEXoZKdzgsHYPl0s5V52Tst+GKzqjebkULT86XMSxejzfISw==}
engines: {node: '>= 12.0.0'}
cpu: [x64]
os: [linux]
2025-02-09 11:38:22 -06:00
lightningcss-linux-x64-musl@1.29.1:
resolution: {integrity: sha512-L0Tx0DtaNUTzXv0lbGCLB/c/qEADanHbu4QdcNOXLIe1i8i22rZRpbT3gpWYsCh9aSL9zFujY/WmEXIatWvXbw==}
engines: {node: '>= 12.0.0'}
cpu: [x64]
os: [linux]
2025-02-09 11:38:22 -06:00
lightningcss-win32-arm64-msvc@1.29.1:
resolution: {integrity: sha512-QoOVnkIEFfbW4xPi+dpdft/zAKmgLgsRHfJalEPYuJDOWf7cLQzYg0DEh8/sn737FaeMJxHZRc1oBreiwZCjog==}
engines: {node: '>= 12.0.0'}
cpu: [arm64]
os: [win32]
lightningcss-win32-x64-msvc@1.29.1:
resolution: {integrity: sha512-NygcbThNBe4JElP+olyTI/doBNGJvLs3bFCRPdvuCcxZCcCZ71B858IHpdm7L1btZex0FvCmM17FK98Y9MRy1Q==}
engines: {node: '>= 12.0.0'}
cpu: [x64]
os: [win32]
2025-02-09 11:38:22 -06:00
lightningcss@1.29.1:
resolution: {integrity: sha512-FmGoeD4S05ewj+AkhTY+D+myDvXI6eL27FjHIjoyUkO/uw7WZD1fBVs0QxeYWa7E17CUHJaYX/RUGISCtcrG4Q==}
engines: {node: '>= 12.0.0'}
2024-07-24 14:05:34 -05:00
lodash.castarray@4.4.0:
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-aVx8ztPv7/2ULbArGJ2Y42bG1mEQ5mGjpdvrbJcJFU3TbYybe+QlLS4pst9zV52ymy2in1KpFPiZnAOATxD4+Q==}
2024-07-24 14:05:34 -05:00
lodash.isplainobject@4.0.6:
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-oSXzaWypCMHkPC3NvBEaPHf0KsA5mvPrOPgQWDsbg8n7orZ290M0BmC/jgRZ4vcJ6DTAhjrsSYgdsW/F+MFOBA==}
2024-07-24 14:05:34 -05:00
lodash.merge@4.6.2:
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-0KpjqXRVvrYyCsX1swR/XTK0va6VQkQM6MNo7PqW77ByjAhoARA8EfrP1N4+KlKj8YS0ZUCtRT/YUuhyYDujIQ==}
2024-12-06 08:23:35 -06:00
nanoid@3.3.8:
resolution: {integrity: sha512-WNLf5Sd8oZxOm+TzppcYk8gVOgP+l58xNy58D0nbUnOxOWRWvlcCV4kUF7ltmI6PsrLl/BgKEyS4mqsGChFN0w==}
engines: {node: ^10 || ^12 || ^13.7 || ^14 || >=15.0.1}
2024-07-24 14:05:34 -05:00
hasBin: true
2025-02-21 12:39:31 -06:00
next@15.2.0-canary.67:
resolution: {integrity: sha512-hKZjcmngKiY/HzHXNN0SGXR9Xio6pirraWu8GqRD24pMiGueY0ykxTbOp0SrqgHDsgWGTOxy3hXCriGiyyVb8w==}
2024-12-06 08:23:35 -06:00
engines: {node: ^18.18.0 || ^19.8.0 || >= 20.0.0}
2024-07-24 14:05:34 -05:00
hasBin: true
2024-03-26 16:15:01 -05:00
peerDependencies:
2024-07-24 14:05:34 -05:00
'@opentelemetry/api': ^1.1.0
'@playwright/test': ^1.41.2
2024-08-13 13:33:05 -05:00
babel-plugin-react-compiler: '*'
2025-02-09 11:38:22 -06:00
react: ^18.2.0 || 19.0.0-rc-de68d2f4-20241204 || ^19.0.0
react-dom: ^18.2.0 || 19.0.0-rc-de68d2f4-20241204 || ^19.0.0
2024-07-24 14:05:34 -05:00
sass: ^1.3.0
peerDependenciesMeta:
'@opentelemetry/api':
optional: true
'@playwright/test':
optional: true
2024-08-13 13:33:05 -05:00
babel-plugin-react-compiler:
optional: true
2024-07-24 14:05:34 -05:00
sass:
optional: true
2024-03-26 16:15:01 -05:00
2024-12-06 08:23:35 -06:00
picocolors@1.1.1:
resolution: {integrity: sha512-xceH2snhtb5M9liqDsmEw56le376mTZkEX/jEb/RxNFyegNul7eNslCXP9FDj/Lcu0X8KEyMceP2ntpaHrDEVA==}
2024-07-24 14:05:34 -05:00
postcss-selector-parser@6.0.10:
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-IQ7TZdoaqbT+LCpShg46jnZVlhWD2w6iQYAcYXfHARZ7X1t/UGhhceQDs5X0cGqKvYlHNOuv7Oa1xmb0oQuA3w==}
engines: {node: '>=4'}
2024-07-24 14:05:34 -05:00
postcss@8.4.31:
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-PS08Iboia9mts/2ygV3eLpY5ghnUcfLV/EXTOW1E2qYxJKGGBUtNjN76FYHnMs36RmARn41bC0AZmn+rR0OVpQ==}
engines: {node: ^10 || ^12 || >=14}
2025-02-21 12:39:31 -06:00
postcss@8.5.3:
resolution: {integrity: sha512-dle9A3yYxlBSrt8Fu+IpjGT8SY8hN0mlaA6GY8t0P5PjIOZemULz/E2Bnm/2dcUOena75OTNkHI76uZBNUUq3A==}
2024-12-06 08:23:35 -06:00
engines: {node: ^10 || ^12 || >=14}
2025-02-09 11:38:22 -06:00
prettier-plugin-tailwindcss@0.6.11:
resolution: {integrity: sha512-YxaYSIvZPAqhrrEpRtonnrXdghZg1irNg4qrjboCXrpybLWVs55cW2N3juhspVJiO0JBvYJT8SYsJpc8OQSnsA==}
2024-12-06 08:23:35 -06:00
engines: {node: '>=14.21.3'}
2024-07-24 14:05:34 -05:00
peerDependencies:
'@ianvs/prettier-plugin-sort-imports': '*'
'@prettier/plugin-pug': '*'
'@shopify/prettier-plugin-liquid': '*'
'@trivago/prettier-plugin-sort-imports': '*'
2025-02-09 11:38:22 -06:00
'@zackad/prettier-plugin-twig': '*'
2024-07-24 14:05:34 -05:00
prettier: ^3.0
prettier-plugin-astro: '*'
prettier-plugin-css-order: '*'
prettier-plugin-import-sort: '*'
prettier-plugin-jsdoc: '*'
prettier-plugin-marko: '*'
2024-12-06 08:23:35 -06:00
prettier-plugin-multiline-arrays: '*'
2024-07-24 14:05:34 -05:00
prettier-plugin-organize-attributes: '*'
prettier-plugin-organize-imports: '*'
prettier-plugin-sort-imports: '*'
prettier-plugin-style-order: '*'
prettier-plugin-svelte: '*'
peerDependenciesMeta:
'@ianvs/prettier-plugin-sort-imports':
optional: true
'@prettier/plugin-pug':
optional: true
'@shopify/prettier-plugin-liquid':
optional: true
'@trivago/prettier-plugin-sort-imports':
optional: true
2025-02-09 11:38:22 -06:00
'@zackad/prettier-plugin-twig':
2024-07-24 14:05:34 -05:00
optional: true
prettier-plugin-astro:
optional: true
prettier-plugin-css-order:
optional: true
prettier-plugin-import-sort:
optional: true
prettier-plugin-jsdoc:
optional: true
prettier-plugin-marko:
optional: true
2024-12-06 08:23:35 -06:00
prettier-plugin-multiline-arrays:
optional: true
2024-07-24 14:05:34 -05:00
prettier-plugin-organize-attributes:
optional: true
prettier-plugin-organize-imports:
optional: true
prettier-plugin-sort-imports:
optional: true
prettier-plugin-style-order:
optional: true
prettier-plugin-svelte:
optional: true
2025-02-21 12:39:31 -06:00
prettier@3.5.1:
resolution: {integrity: sha512-hPpFQvHwL3Qv5AdRvBFMhnKo4tYxp0ReXiPn2bxkiohEX6mBeBwEpBSQTkD458RaaDKQMYSp4hX4UtfUTA5wDw==}
2024-12-06 08:23:35 -06:00
engines: {node: '>=14'}
2024-07-24 14:05:34 -05:00
hasBin: true
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"](https://github.com/vercel/commerce/blob/d1d9e8c4343e70d72df6e00ec95f6ea4efbb7c54/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 23:00:47 -04:00
2024-12-06 08:23:35 -06:00
react-dom@19.0.0:
resolution: {integrity: sha512-4GV5sHFG0e/0AD4X+ySy6UJd3jVl1iNsNHdpad0qhABJ11twS3TTBnseqsKurKcsNqCEFeGL3uLpVChpIO3QfQ==}
2024-07-24 14:05:34 -05:00
peerDependencies:
2024-12-06 08:23:35 -06:00
react: ^19.0.0
2024-12-06 08:23:35 -06:00
react@19.0.0:
resolution: {integrity: sha512-V8AVnmPIICiWpGfm6GLzCR/W5FXLchHop40W4nXBmdlEceh16rCN8O8LNWm5bh5XUX91fh7KpA+W0TgMKmgTpQ==}
engines: {node: '>=0.10.0'}
2024-12-06 08:23:35 -06:00
scheduler@0.25.0:
resolution: {integrity: sha512-xFVuu11jh+xcO7JOAGJNOXld8/TcEHK/4CituBUeUb5hqxJLj9YuemAEuvm9gQ/+pgXYfbQuqAkiYu+u7YEsNA==}
2024-08-13 13:33:05 -05:00
2025-02-09 11:38:22 -06:00
semver@7.7.1:
resolution: {integrity: sha512-hlq8tAfn0m/61p4BVRcPzIGr6LKiMwo4VM6dGi6pt4qcRkmNzTcWq6eCEjEh+qXjkMDvPlOFFSGwQjoEa6gyMA==}
2024-12-06 08:23:35 -06:00
engines: {node: '>=10'}
2024-08-13 13:33:05 -05:00
hasBin: true
2024-10-15 22:07:55 -05:00
sharp@0.33.5:
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-haPVm1EkS9pgvHrQ/F3Xy+hgcuMV0Wm9vfIBSiwZ05k+xgb0PkBQpGsAA/oWdDobNaZTH5ppvHtzCFbnSEwHVw==}
engines: {node: ^18.17.0 || ^20.3.0 || >=21.0.0}
2024-08-13 13:33:05 -05:00
simple-swizzle@0.2.2:
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-JA//kQgZtbuY83m+xT+tXJkmJncGMTFT+C+g2h2R9uxkYIrE2yy9sgmcLhCnw57/WSD+Eh3J97FPEDFnbXnDUg==}
2025-02-21 12:39:31 -06:00
sonner@2.0.1:
resolution: {integrity: sha512-FRBphaehZ5tLdLcQ8g2WOIRE+Y7BCfWi5Zyd8bCvBjiW8TxxAyoWZIxS661Yz6TGPqFQ4VLzOF89WEYhfynSFQ==}
peerDependencies:
2024-12-06 08:23:35 -06:00
react: ^18.0.0 || ^19.0.0 || ^19.0.0-rc
react-dom: ^18.0.0 || ^19.0.0 || ^19.0.0-rc
2024-12-06 08:23:35 -06:00
source-map-js@1.2.1:
resolution: {integrity: sha512-UXWMKhLOwVKb728IUtQPXxfYU+usdybtUrK/8uGE8CQMvrhOpwvzDBwj0QhSL7MQc7vIsISBG8VQ8+IDQxpfQA==}
engines: {node: '>=0.10.0'}
2024-07-24 14:05:34 -05:00
streamsearch@1.1.0:
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-Mcc5wHehp9aXz1ax6bZUyY5afg9u2rv5cqQI3mRrYkGC8rW2hM02jWuwjtL++LS5qinSyhj2QfLyNsuc+VsExg==}
engines: {node: '>=10.0.0'}
2024-03-26 16:15:01 -05:00
2024-08-13 13:33:05 -05:00
styled-jsx@5.1.6:
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-qSVyDTeMotdvQYoHWLNGwRFJHC+i+ZvdBRYosOFgC+Wg1vx4frN2/RG/NA7SYqqvKNLf39P2LSRA2pu6n0XYZA==}
engines: {node: '>= 12.0.0'}
2024-07-24 14:05:34 -05:00
peerDependencies:
'@babel/core': '*'
babel-plugin-macros: '*'
2024-08-13 13:33:05 -05:00
react: '>= 16.8.0 || 17.x.x || ^18.0.0-0 || ^19.0.0-0'
2024-07-24 14:05:34 -05:00
peerDependenciesMeta:
'@babel/core':
optional: true
babel-plugin-macros:
optional: true
2024-07-24 14:05:34 -05:00
tabbable@6.2.0:
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-Cat63mxsVJlzYvN51JmVXIgNoUokrIaT2zLclCXjRd8boZ0004U4KCs/sToJ75C6sdlByWxpYnb5Boif1VSFew==}
2025-02-21 12:39:31 -06:00
tailwindcss@4.0.8:
resolution: {integrity: sha512-Me7N5CKR+D2A1xdWA5t5+kjjT7bwnxZOE6/yDI/ixJdJokszsn2n++mdU5yJwrsTpqFX2B9ZNMBJDwcqk9C9lw==}
2025-02-09 11:38:22 -06:00
tapable@2.2.1:
resolution: {integrity: sha512-GNzQvQTOIP6RyTfE2Qxb8ZVlNmw0n88vp1szwWRimP02mnTsx3Wtn5qRdqY9w2XduFNUgvOwhNnQsjwCp+kqaQ==}
engines: {node: '>=6'}
2024-12-06 08:23:35 -06:00
tslib@2.8.1:
resolution: {integrity: sha512-oJFu94HQb+KVduSUQL7wnpmqnfmLsOA/nAh6b6EH0wCEoK0/mPeXU6c3wKDV83MkOuHPRHtSXKKU99IBazS/2w==}
2025-02-09 11:38:22 -06:00
typescript@5.7.3:
resolution: {integrity: sha512-84MVSjMEHP+FQRPy3pX9sTVV/INIex71s9TL2Gm5FG/WG1SqXeKyZ0k7/blY/4FdOzI12CBy1vGc4og/eus0fw==}
2024-12-06 08:23:35 -06:00
engines: {node: '>=14.17'}
hasBin: true
2024-12-06 08:23:35 -06:00
undici-types@6.20.0:
resolution: {integrity: sha512-Ny6QZ2Nju20vw1SRHe3d9jVu6gJ+4e3+MMpqu7pqE5HT6WsTSlce++GQmK5UXS8mzV8DSYHrQH+Xrf2jVcuKNg==}
2024-07-24 14:05:34 -05:00
util-deprecate@1.0.2:
2024-12-06 08:23:35 -06:00
resolution: {integrity: sha512-EPD5q1uXyFxJpCrLnCc1nHnq3gOa6DZBocAIiI2TaSCA7VCJ1UJDMagCzIkXNsUYfD1daK//LTEQ8xiIbrHtcw==}
2024-07-24 14:05:34 -05:00
snapshots:
2024-12-06 08:23:35 -06:00
2024-07-24 14:05:34 -05:00
'@alloc/quick-lru@5.2.0': {}
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"](https://github.com/vercel/commerce/blob/d1d9e8c4343e70d72df6e00ec95f6ea4efbb7c54/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 23:00:47 -04:00
2024-12-06 08:23:35 -06:00
'@emnapi/runtime@1.3.1':
2024-08-13 13:33:05 -05:00
dependencies:
2024-12-06 08:23:35 -06:00
tslib: 2.8.1
2024-08-13 13:33:05 -05:00
optional: true
2025-02-09 11:38:22 -06:00
'@floating-ui/core@1.6.9':
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"](https://github.com/vercel/commerce/blob/d1d9e8c4343e70d72df6e00ec95f6ea4efbb7c54/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 23:00:47 -04:00
dependencies:
2025-02-09 11:38:22 -06:00
'@floating-ui/utils': 0.2.9
2025-02-09 11:38:22 -06:00
'@floating-ui/dom@1.6.13':
dependencies:
2025-02-09 11:38:22 -06:00
'@floating-ui/core': 1.6.9
'@floating-ui/utils': 0.2.9
2024-12-06 08:23:35 -06:00
'@floating-ui/react-dom@2.1.2(react-dom@19.0.0(react@19.0.0))(react@19.0.0)':
dependencies:
2025-02-09 11:38:22 -06:00
'@floating-ui/dom': 1.6.13
2024-12-06 08:23:35 -06:00
react: 19.0.0
react-dom: 19.0.0(react@19.0.0)
2024-12-06 08:23:35 -06:00
'@floating-ui/react@0.26.28(react-dom@19.0.0(react@19.0.0))(react@19.0.0)':
dependencies:
2024-12-06 08:23:35 -06:00
'@floating-ui/react-dom': 2.1.2(react-dom@19.0.0(react@19.0.0))(react@19.0.0)
2025-02-09 11:38:22 -06:00
'@floating-ui/utils': 0.2.9
2024-12-06 08:23:35 -06:00
react: 19.0.0
react-dom: 19.0.0(react@19.0.0)
2024-07-24 14:05:34 -05:00
tabbable: 6.2.0
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"](https://github.com/vercel/commerce/blob/d1d9e8c4343e70d72df6e00ec95f6ea4efbb7c54/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 23:00:47 -04:00
2025-02-09 11:38:22 -06:00
'@floating-ui/utils@0.2.9': {}
2024-12-06 08:23:35 -06:00
'@headlessui/react@2.2.0(react-dom@19.0.0(react@19.0.0))(react@19.0.0)':
2024-08-13 13:33:05 -05:00
dependencies:
2024-12-06 08:23:35 -06:00
'@floating-ui/react': 0.26.28(react-dom@19.0.0(react@19.0.0))(react@19.0.0)
2025-02-09 11:38:22 -06:00
'@react-aria/focus': 3.19.1(react-dom@19.0.0(react@19.0.0))(react@19.0.0)
'@react-aria/interactions': 3.23.0(react-dom@19.0.0(react@19.0.0))(react@19.0.0)
'@tanstack/react-virtual': 3.13.0(react-dom@19.0.0(react@19.0.0))(react@19.0.0)
2024-12-06 08:23:35 -06:00
react: 19.0.0
react-dom: 19.0.0(react@19.0.0)
2024-08-13 13:33:05 -05:00
2024-12-06 08:23:35 -06:00
'@heroicons/react@2.2.0(react@19.0.0)':
dependencies:
2024-12-06 08:23:35 -06:00
react: 19.0.0
2024-08-13 13:33:05 -05:00
2024-10-15 22:07:55 -05:00
'@img/sharp-darwin-arm64@0.33.5':
2024-08-13 13:33:05 -05:00
optionalDependencies:
2024-10-15 22:07:55 -05:00
'@img/sharp-libvips-darwin-arm64': 1.0.4
2024-08-13 13:33:05 -05:00
optional: true
2024-10-15 22:07:55 -05:00
'@img/sharp-darwin-x64@0.33.5':
2024-08-13 13:33:05 -05:00
optionalDependencies:
2024-10-15 22:07:55 -05:00
'@img/sharp-libvips-darwin-x64': 1.0.4
2024-08-13 13:33:05 -05:00
optional: true
2024-10-15 22:07:55 -05:00
'@img/sharp-libvips-darwin-arm64@1.0.4':
2024-08-13 13:33:05 -05:00
optional: true
2024-10-15 22:07:55 -05:00
'@img/sharp-libvips-darwin-x64@1.0.4':
2024-08-13 13:33:05 -05:00
optional: true
2024-10-15 22:07:55 -05:00
'@img/sharp-libvips-linux-arm64@1.0.4':
2024-08-13 13:33:05 -05:00
optional: true
2024-10-15 22:07:55 -05:00
'@img/sharp-libvips-linux-arm@1.0.5':
2024-08-13 13:33:05 -05:00
optional: true
2024-10-15 22:07:55 -05:00
'@img/sharp-libvips-linux-s390x@1.0.4':
2024-08-13 13:33:05 -05:00
optional: true
2024-10-15 22:07:55 -05:00
'@img/sharp-libvips-linux-x64@1.0.4':
2024-08-13 13:33:05 -05:00
optional: true
2024-10-15 22:07:55 -05:00
'@img/sharp-libvips-linuxmusl-arm64@1.0.4':
2024-08-13 13:33:05 -05:00
optional: true
2024-10-15 22:07:55 -05:00
'@img/sharp-libvips-linuxmusl-x64@1.0.4':
2024-08-13 13:33:05 -05:00
optional: true
2024-10-15 22:07:55 -05:00
'@img/sharp-linux-arm64@0.33.5':
2024-08-13 13:33:05 -05:00
optionalDependencies:
2024-10-15 22:07:55 -05:00
'@img/sharp-libvips-linux-arm64': 1.0.4
2024-08-13 13:33:05 -05:00
optional: true
2024-10-15 22:07:55 -05:00
'@img/sharp-linux-arm@0.33.5':
2024-08-13 13:33:05 -05:00
optionalDependencies:
2024-10-15 22:07:55 -05:00
'@img/sharp-libvips-linux-arm': 1.0.5
2024-08-13 13:33:05 -05:00
optional: true
2024-10-15 22:07:55 -05:00
'@img/sharp-linux-s390x@0.33.5':
2024-08-13 13:33:05 -05:00
optionalDependencies:
2024-10-15 22:07:55 -05:00
'@img/sharp-libvips-linux-s390x': 1.0.4
2024-08-13 13:33:05 -05:00
optional: true
2024-10-15 22:07:55 -05:00
'@img/sharp-linux-x64@0.33.5':
2024-08-13 13:33:05 -05:00
optionalDependencies:
2024-10-15 22:07:55 -05:00
'@img/sharp-libvips-linux-x64': 1.0.4
2024-08-13 13:33:05 -05:00
optional: true
2024-10-15 22:07:55 -05:00
'@img/sharp-linuxmusl-arm64@0.33.5':
2024-08-13 13:33:05 -05:00
optionalDependencies:
2024-10-15 22:07:55 -05:00
'@img/sharp-libvips-linuxmusl-arm64': 1.0.4
2024-08-13 13:33:05 -05:00
optional: true
2024-10-15 22:07:55 -05:00
'@img/sharp-linuxmusl-x64@0.33.5':
2024-08-13 13:33:05 -05:00
optionalDependencies:
2024-10-15 22:07:55 -05:00
'@img/sharp-libvips-linuxmusl-x64': 1.0.4
2024-08-13 13:33:05 -05:00
optional: true
2024-10-15 22:07:55 -05:00
'@img/sharp-wasm32@0.33.5':
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"](https://github.com/vercel/commerce/blob/d1d9e8c4343e70d72df6e00ec95f6ea4efbb7c54/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 23:00:47 -04:00
dependencies:
2024-12-06 08:23:35 -06:00
'@emnapi/runtime': 1.3.1
2024-08-13 13:33:05 -05:00
optional: true
2024-10-15 22:07:55 -05:00
'@img/sharp-win32-ia32@0.33.5':
2024-08-13 13:33:05 -05:00
optional: true
2024-10-15 22:07:55 -05:00
'@img/sharp-win32-x64@0.33.5':
2024-08-13 13:33:05 -05:00
optional: true
2025-02-21 12:39:31 -06:00
'@next/env@15.2.0-canary.67': {}
2025-02-21 12:39:31 -06:00
'@next/swc-darwin-arm64@15.2.0-canary.67':
2024-07-24 14:05:34 -05:00
optional: true
2025-02-21 12:39:31 -06:00
'@next/swc-darwin-x64@15.2.0-canary.67':
2024-07-24 14:05:34 -05:00
optional: true
2025-02-21 12:39:31 -06:00
'@next/swc-linux-arm64-gnu@15.2.0-canary.67':
2024-07-24 14:05:34 -05:00
optional: true
2024-03-26 16:15:01 -05:00
2025-02-21 12:39:31 -06:00
'@next/swc-linux-arm64-musl@15.2.0-canary.67':
2024-07-24 14:05:34 -05:00
optional: true
2024-04-17 21:54:09 -05:00
2025-02-21 12:39:31 -06:00
'@next/swc-linux-x64-gnu@15.2.0-canary.67':
2024-07-24 14:05:34 -05:00
optional: true
2025-02-21 12:39:31 -06:00
'@next/swc-linux-x64-musl@15.2.0-canary.67':
2024-07-24 14:05:34 -05:00
optional: true
2024-03-26 16:15:01 -05:00
2025-02-21 12:39:31 -06:00
'@next/swc-win32-arm64-msvc@15.2.0-canary.67':
2024-07-24 14:05:34 -05:00
optional: true
2025-02-21 12:39:31 -06:00
'@next/swc-win32-x64-msvc@15.2.0-canary.67':
2024-07-24 14:05:34 -05:00
optional: true
2025-02-09 11:38:22 -06:00
'@react-aria/focus@3.19.1(react-dom@19.0.0(react@19.0.0))(react@19.0.0)':
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"](https://github.com/vercel/commerce/blob/d1d9e8c4343e70d72df6e00ec95f6ea4efbb7c54/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 23:00:47 -04:00
dependencies:
2025-02-09 11:38:22 -06:00
'@react-aria/interactions': 3.23.0(react-dom@19.0.0(react@19.0.0))(react@19.0.0)
'@react-aria/utils': 3.27.0(react-dom@19.0.0(react@19.0.0))(react@19.0.0)
'@react-types/shared': 3.27.0(react@19.0.0)
2024-12-06 08:23:35 -06:00
'@swc/helpers': 0.5.15
2024-07-24 14:05:34 -05:00
clsx: 2.1.1
2024-12-06 08:23:35 -06:00
react: 19.0.0
2025-02-09 11:38:22 -06:00
react-dom: 19.0.0(react@19.0.0)
2025-02-09 11:38:22 -06:00
'@react-aria/interactions@3.23.0(react-dom@19.0.0(react@19.0.0))(react@19.0.0)':
2024-07-24 14:05:34 -05:00
dependencies:
2024-12-06 08:23:35 -06:00
'@react-aria/ssr': 3.9.7(react@19.0.0)
2025-02-09 11:38:22 -06:00
'@react-aria/utils': 3.27.0(react-dom@19.0.0(react@19.0.0))(react@19.0.0)
'@react-types/shared': 3.27.0(react@19.0.0)
2024-12-06 08:23:35 -06:00
'@swc/helpers': 0.5.15
react: 19.0.0
2025-02-09 11:38:22 -06:00
react-dom: 19.0.0(react@19.0.0)
2024-12-06 08:23:35 -06:00
'@react-aria/ssr@3.9.7(react@19.0.0)':
2024-07-24 14:05:34 -05:00
dependencies:
2024-12-06 08:23:35 -06:00
'@swc/helpers': 0.5.15
react: 19.0.0
2025-02-09 11:38:22 -06:00
'@react-aria/utils@3.27.0(react-dom@19.0.0(react@19.0.0))(react@19.0.0)':
dependencies:
2024-12-06 08:23:35 -06:00
'@react-aria/ssr': 3.9.7(react@19.0.0)
'@react-stately/utils': 3.10.5(react@19.0.0)
2025-02-09 11:38:22 -06:00
'@react-types/shared': 3.27.0(react@19.0.0)
2024-12-06 08:23:35 -06:00
'@swc/helpers': 0.5.15
2024-07-24 14:05:34 -05:00
clsx: 2.1.1
2024-12-06 08:23:35 -06:00
react: 19.0.0
2025-02-09 11:38:22 -06:00
react-dom: 19.0.0(react@19.0.0)
2024-12-06 08:23:35 -06:00
'@react-stately/utils@3.10.5(react@19.0.0)':
2024-07-24 14:05:34 -05:00
dependencies:
2024-12-06 08:23:35 -06:00
'@swc/helpers': 0.5.15
react: 19.0.0
2025-02-09 11:38:22 -06:00
'@react-types/shared@3.27.0(react@19.0.0)':
2024-07-24 14:05:34 -05:00
dependencies:
2024-12-06 08:23:35 -06:00
react: 19.0.0
2024-07-24 14:05:34 -05:00
'@swc/counter@0.1.3': {}
2024-12-06 08:23:35 -06:00
'@swc/helpers@0.5.15':
2024-10-15 22:07:55 -05:00
dependencies:
2024-12-06 08:23:35 -06:00
tslib: 2.8.1
2024-10-15 22:07:55 -05:00
2025-02-21 12:39:31 -06:00
'@tailwindcss/container-queries@0.1.1(tailwindcss@4.0.8)':
dependencies:
2025-02-21 12:39:31 -06:00
tailwindcss: 4.0.8
2025-02-21 12:39:31 -06:00
'@tailwindcss/node@4.0.8':
dependencies:
2025-02-09 11:38:22 -06:00
enhanced-resolve: 5.18.1
jiti: 2.4.2
2025-02-21 12:39:31 -06:00
tailwindcss: 4.0.8
2025-02-21 12:39:31 -06:00
'@tailwindcss/oxide-android-arm64@4.0.8':
2025-02-09 11:38:22 -06:00
optional: true
2025-02-21 12:39:31 -06:00
'@tailwindcss/oxide-darwin-arm64@4.0.8':
2025-02-09 11:38:22 -06:00
optional: true
2024-12-06 08:23:35 -06:00
2025-02-21 12:39:31 -06:00
'@tailwindcss/oxide-darwin-x64@4.0.8':
2025-02-09 11:38:22 -06:00
optional: true
2024-07-24 14:05:34 -05:00
2025-02-21 12:39:31 -06:00
'@tailwindcss/oxide-freebsd-x64@4.0.8':
2025-02-09 11:38:22 -06:00
optional: true
2024-12-06 08:23:35 -06:00
2025-02-21 12:39:31 -06:00
'@tailwindcss/oxide-linux-arm-gnueabihf@4.0.8':
2025-02-09 11:38:22 -06:00
optional: true
2025-02-21 12:39:31 -06:00
'@tailwindcss/oxide-linux-arm64-gnu@4.0.8':
2025-02-09 11:38:22 -06:00
optional: true
2024-07-24 14:05:34 -05:00
2025-02-21 12:39:31 -06:00
'@tailwindcss/oxide-linux-arm64-musl@4.0.8':
2025-02-09 11:38:22 -06:00
optional: true
2024-07-24 14:05:34 -05:00
2025-02-21 12:39:31 -06:00
'@tailwindcss/oxide-linux-x64-gnu@4.0.8':
2025-02-09 11:38:22 -06:00
optional: true
2025-02-21 12:39:31 -06:00
'@tailwindcss/oxide-linux-x64-musl@4.0.8':
2025-02-09 11:38:22 -06:00
optional: true
2024-07-24 14:05:34 -05:00
2025-02-21 12:39:31 -06:00
'@tailwindcss/oxide-win32-arm64-msvc@4.0.8':
2025-02-09 11:38:22 -06:00
optional: true
2024-07-24 14:05:34 -05:00
2025-02-21 12:39:31 -06:00
'@tailwindcss/oxide-win32-x64-msvc@4.0.8':
2025-02-09 11:38:22 -06:00
optional: true
2024-07-24 14:05:34 -05:00
2025-02-21 12:39:31 -06:00
'@tailwindcss/oxide@4.0.8':
2025-02-09 11:38:22 -06:00
optionalDependencies:
2025-02-21 12:39:31 -06:00
'@tailwindcss/oxide-android-arm64': 4.0.8
'@tailwindcss/oxide-darwin-arm64': 4.0.8
'@tailwindcss/oxide-darwin-x64': 4.0.8
'@tailwindcss/oxide-freebsd-x64': 4.0.8
'@tailwindcss/oxide-linux-arm-gnueabihf': 4.0.8
'@tailwindcss/oxide-linux-arm64-gnu': 4.0.8
'@tailwindcss/oxide-linux-arm64-musl': 4.0.8
'@tailwindcss/oxide-linux-x64-gnu': 4.0.8
'@tailwindcss/oxide-linux-x64-musl': 4.0.8
'@tailwindcss/oxide-win32-arm64-msvc': 4.0.8
'@tailwindcss/oxide-win32-x64-msvc': 4.0.8
'@tailwindcss/postcss@4.0.8':
2025-02-09 11:38:22 -06:00
dependencies:
'@alloc/quick-lru': 5.2.0
2025-02-21 12:39:31 -06:00
'@tailwindcss/node': 4.0.8
'@tailwindcss/oxide': 4.0.8
2025-02-09 11:38:22 -06:00
lightningcss: 1.29.1
2025-02-21 12:39:31 -06:00
postcss: 8.5.3
tailwindcss: 4.0.8
2025-02-21 12:39:31 -06:00
'@tailwindcss/typography@0.5.16(tailwindcss@4.0.8)':
dependencies:
2025-02-09 11:38:22 -06:00
lodash.castarray: 4.4.0
lodash.isplainobject: 4.0.6
lodash.merge: 4.6.2
postcss-selector-parser: 6.0.10
2025-02-21 12:39:31 -06:00
tailwindcss: 4.0.8
2025-02-09 11:38:22 -06:00
'@tanstack/react-virtual@3.13.0(react-dom@19.0.0(react@19.0.0))(react@19.0.0)':
dependencies:
'@tanstack/virtual-core': 3.13.0
react: 19.0.0
react-dom: 19.0.0(react@19.0.0)
2024-07-24 14:05:34 -05:00
2025-02-09 11:38:22 -06:00
'@tanstack/virtual-core@3.13.0': {}
2024-07-24 14:05:34 -05:00
2025-02-21 12:39:31 -06:00
'@types/node@22.13.4':
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"](https://github.com/vercel/commerce/blob/d1d9e8c4343e70d72df6e00ec95f6ea4efbb7c54/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 23:00:47 -04:00
dependencies:
2025-02-09 11:38:22 -06:00
undici-types: 6.20.0
2025-02-21 12:39:31 -06:00
'@types/react-dom@19.0.4(@types/react@19.0.10)':
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"](https://github.com/vercel/commerce/blob/d1d9e8c4343e70d72df6e00ec95f6ea4efbb7c54/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 23:00:47 -04:00
dependencies:
2025-02-21 12:39:31 -06:00
'@types/react': 19.0.10
2025-02-21 12:39:31 -06:00
'@types/react@19.0.10':
dependencies:
2025-02-09 11:38:22 -06:00
csstype: 3.1.3
2024-07-24 14:05:34 -05:00
busboy@1.6.0:
dependencies:
2024-07-24 14:05:34 -05:00
streamsearch: 1.1.0
2025-02-21 12:39:31 -06:00
caniuse-lite@1.0.30001700: {}
2024-07-24 14:05:34 -05:00
client-only@0.0.1: {}
2024-07-24 14:05:34 -05:00
clsx@2.1.1: {}
2024-07-24 14:05:34 -05:00
color-convert@2.0.1:
dependencies:
color-name: 1.1.4
2025-02-09 11:38:22 -06:00
optional: true
2025-02-09 11:38:22 -06:00
color-name@1.1.4:
optional: true
2024-08-13 13:33:05 -05:00
color-string@1.9.1:
dependencies:
color-name: 1.1.4
simple-swizzle: 0.2.2
optional: true
color@4.2.3:
dependencies:
color-convert: 2.0.1
color-string: 1.9.1
optional: true
2024-07-24 14:05:34 -05:00
cssesc@3.0.0: {}
2024-07-24 14:05:34 -05:00
csstype@3.1.3: {}
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"](https://github.com/vercel/commerce/blob/d1d9e8c4343e70d72df6e00ec95f6ea4efbb7c54/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 23:00:47 -04:00
2025-02-09 11:38:22 -06:00
detect-libc@1.0.3: {}
2024-08-13 13:33:05 -05:00
detect-libc@2.0.3:
optional: true
2025-02-09 11:38:22 -06:00
enhanced-resolve@5.18.1:
dependencies:
2025-02-09 11:38:22 -06:00
graceful-fs: 4.2.11
tapable: 2.2.1
2025-02-21 12:39:31 -06:00
geist@1.3.1(next@15.2.0-canary.67(react-dom@19.0.0(react@19.0.0))(react@19.0.0)):
dependencies:
2025-02-21 12:39:31 -06:00
next: 15.2.0-canary.67(react-dom@19.0.0(react@19.0.0))(react@19.0.0)
2025-02-09 11:38:22 -06:00
graceful-fs@4.2.11: {}
2025-02-09 11:38:22 -06:00
is-arrayish@0.3.2:
2024-07-24 14:05:34 -05:00
optional: true
2025-02-09 11:38:22 -06:00
jiti@2.4.2: {}
2025-02-09 11:38:22 -06:00
lightningcss-darwin-arm64@1.29.1:
optional: true
2024-03-26 16:15:01 -05:00
2025-02-09 11:38:22 -06:00
lightningcss-darwin-x64@1.29.1:
optional: true
2024-07-24 14:05:34 -05:00
2025-02-09 11:38:22 -06:00
lightningcss-freebsd-x64@1.29.1:
2024-08-13 13:33:05 -05:00
optional: true
2025-02-09 11:38:22 -06:00
lightningcss-linux-arm-gnueabihf@1.29.1:
optional: true
2024-07-24 14:05:34 -05:00
2025-02-09 11:38:22 -06:00
lightningcss-linux-arm64-gnu@1.29.1:
optional: true
2025-02-09 11:38:22 -06:00
lightningcss-linux-arm64-musl@1.29.1:
optional: true
2025-02-09 11:38:22 -06:00
lightningcss-linux-x64-gnu@1.29.1:
optional: true
2024-07-24 14:05:34 -05:00
2025-02-09 11:38:22 -06:00
lightningcss-linux-x64-musl@1.29.1:
optional: true
2025-02-09 11:38:22 -06:00
lightningcss-win32-arm64-msvc@1.29.1:
optional: true
2025-02-09 11:38:22 -06:00
lightningcss-win32-x64-msvc@1.29.1:
optional: true
2025-02-09 11:38:22 -06:00
lightningcss@1.29.1:
dependencies:
2025-02-09 11:38:22 -06:00
detect-libc: 1.0.3
2024-07-24 14:05:34 -05:00
optionalDependencies:
2025-02-09 11:38:22 -06:00
lightningcss-darwin-arm64: 1.29.1
lightningcss-darwin-x64: 1.29.1
lightningcss-freebsd-x64: 1.29.1
lightningcss-linux-arm-gnueabihf: 1.29.1
lightningcss-linux-arm64-gnu: 1.29.1
lightningcss-linux-arm64-musl: 1.29.1
lightningcss-linux-x64-gnu: 1.29.1
lightningcss-linux-x64-musl: 1.29.1
lightningcss-win32-arm64-msvc: 1.29.1
lightningcss-win32-x64-msvc: 1.29.1
2024-07-24 14:05:34 -05:00
lodash.castarray@4.4.0: {}
lodash.isplainobject@4.0.6: {}
lodash.merge@4.6.2: {}
2024-12-06 08:23:35 -06:00
nanoid@3.3.8: {}
2024-07-24 14:05:34 -05:00
2025-02-21 12:39:31 -06:00
next@15.2.0-canary.67(react-dom@19.0.0(react@19.0.0))(react@19.0.0):
dependencies:
2025-02-21 12:39:31 -06:00
'@next/env': 15.2.0-canary.67
2024-08-13 13:33:05 -05:00
'@swc/counter': 0.1.3
2025-02-09 11:38:22 -06:00
'@swc/helpers': 0.5.15
2024-07-24 14:05:34 -05:00
busboy: 1.6.0
2025-02-21 12:39:31 -06:00
caniuse-lite: 1.0.30001700
2024-07-24 14:05:34 -05:00
postcss: 8.4.31
2024-12-06 08:23:35 -06:00
react: 19.0.0
react-dom: 19.0.0(react@19.0.0)
styled-jsx: 5.1.6(react@19.0.0)
2024-07-24 14:05:34 -05:00
optionalDependencies:
2025-02-21 12:39:31 -06:00
'@next/swc-darwin-arm64': 15.2.0-canary.67
'@next/swc-darwin-x64': 15.2.0-canary.67
'@next/swc-linux-arm64-gnu': 15.2.0-canary.67
'@next/swc-linux-arm64-musl': 15.2.0-canary.67
'@next/swc-linux-x64-gnu': 15.2.0-canary.67
'@next/swc-linux-x64-musl': 15.2.0-canary.67
'@next/swc-win32-arm64-msvc': 15.2.0-canary.67
'@next/swc-win32-x64-msvc': 15.2.0-canary.67
2024-10-15 22:07:55 -05:00
sharp: 0.33.5
2024-07-24 14:05:34 -05:00
transitivePeerDependencies:
- '@babel/core'
- babel-plugin-macros
2024-12-06 08:23:35 -06:00
picocolors@1.1.1: {}
2024-07-24 14:05:34 -05:00
postcss-selector-parser@6.0.10:
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"](https://github.com/vercel/commerce/blob/d1d9e8c4343e70d72df6e00ec95f6ea4efbb7c54/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 23:00:47 -04:00
dependencies:
2024-07-24 14:05:34 -05:00
cssesc: 3.0.0
util-deprecate: 1.0.2
2024-07-24 14:05:34 -05:00
postcss@8.4.31:
dependencies:
2024-12-06 08:23:35 -06:00
nanoid: 3.3.8
picocolors: 1.1.1
source-map-js: 1.2.1
2025-02-21 12:39:31 -06:00
postcss@8.5.3:
2023-10-27 14:11:18 -05:00
dependencies:
2024-12-06 08:23:35 -06:00
nanoid: 3.3.8
picocolors: 1.1.1
source-map-js: 1.2.1
2023-10-27 14:11:18 -05:00
2025-02-21 12:39:31 -06:00
prettier-plugin-tailwindcss@0.6.11(prettier@3.5.1):
dependencies:
2025-02-21 12:39:31 -06:00
prettier: 3.5.1
2025-02-21 12:39:31 -06:00
prettier@3.5.1: {}
2024-12-06 08:23:35 -06:00
react-dom@19.0.0(react@19.0.0):
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"](https://github.com/vercel/commerce/blob/d1d9e8c4343e70d72df6e00ec95f6ea4efbb7c54/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 23:00:47 -04:00
dependencies:
2024-12-06 08:23:35 -06:00
react: 19.0.0
scheduler: 0.25.0
2024-12-06 08:23:35 -06:00
react@19.0.0: {}
2023-10-27 14:11:18 -05:00
2024-12-06 08:23:35 -06:00
scheduler@0.25.0: {}
2024-08-13 13:33:05 -05:00
2025-02-09 11:38:22 -06:00
semver@7.7.1:
2024-08-13 13:33:05 -05:00
optional: true
2024-10-15 22:07:55 -05:00
sharp@0.33.5:
2024-07-24 14:05:34 -05:00
dependencies:
2024-08-13 13:33:05 -05:00
color: 4.2.3
detect-libc: 2.0.3
2025-02-09 11:38:22 -06:00
semver: 7.7.1
2024-08-13 13:33:05 -05:00
optionalDependencies:
2024-10-15 22:07:55 -05:00
'@img/sharp-darwin-arm64': 0.33.5
'@img/sharp-darwin-x64': 0.33.5
'@img/sharp-libvips-darwin-arm64': 1.0.4
'@img/sharp-libvips-darwin-x64': 1.0.4
'@img/sharp-libvips-linux-arm': 1.0.5
'@img/sharp-libvips-linux-arm64': 1.0.4
'@img/sharp-libvips-linux-s390x': 1.0.4
'@img/sharp-libvips-linux-x64': 1.0.4
'@img/sharp-libvips-linuxmusl-arm64': 1.0.4
'@img/sharp-libvips-linuxmusl-x64': 1.0.4
'@img/sharp-linux-arm': 0.33.5
'@img/sharp-linux-arm64': 0.33.5
'@img/sharp-linux-s390x': 0.33.5
'@img/sharp-linux-x64': 0.33.5
'@img/sharp-linuxmusl-arm64': 0.33.5
'@img/sharp-linuxmusl-x64': 0.33.5
'@img/sharp-wasm32': 0.33.5
'@img/sharp-win32-ia32': 0.33.5
'@img/sharp-win32-x64': 0.33.5
2024-08-13 13:33:05 -05:00
optional: true
2024-08-13 13:33:05 -05:00
simple-swizzle@0.2.2:
dependencies:
is-arrayish: 0.3.2
optional: true
2025-02-21 12:39:31 -06:00
sonner@2.0.1(react-dom@19.0.0(react@19.0.0))(react@19.0.0):
dependencies:
2024-12-06 08:23:35 -06:00
react: 19.0.0
react-dom: 19.0.0(react@19.0.0)
2024-12-06 08:23:35 -06:00
source-map-js@1.2.1: {}
2024-07-24 14:05:34 -05:00
streamsearch@1.1.0: {}
2024-12-06 08:23:35 -06:00
styled-jsx@5.1.6(react@19.0.0):
dependencies:
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"](https://github.com/vercel/commerce/blob/d1d9e8c4343e70d72df6e00ec95f6ea4efbb7c54/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 23:00:47 -04:00
client-only: 0.0.1
2024-12-06 08:23:35 -06:00
react: 19.0.0
2024-07-24 14:05:34 -05:00
tabbable@6.2.0: {}
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"](https://github.com/vercel/commerce/blob/d1d9e8c4343e70d72df6e00ec95f6ea4efbb7c54/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 23:00:47 -04:00
2025-02-21 12:39:31 -06:00
tailwindcss@4.0.8: {}
2023-07-24 21:40:29 -05:00
2025-02-09 11:38:22 -06:00
tapable@2.2.1: {}
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"](https://github.com/vercel/commerce/blob/d1d9e8c4343e70d72df6e00ec95f6ea4efbb7c54/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 23:00:47 -04:00
2024-12-06 08:23:35 -06:00
tslib@2.8.1: {}
2024-10-15 22:07:55 -05:00
2025-02-09 11:38:22 -06:00
typescript@5.7.3: {}
2024-12-06 08:23:35 -06:00
undici-types@6.20.0: {}
2023-05-08 07:22:31 -07:00
2024-07-24 14:05:34 -05:00
util-deprecate@1.0.2: {}