Having the useCart returns promises would improve my DX a lot

[pnodet]

hydrogen-react offers a lot of flexibility over the full hydrogen frameworks (id: building nextjs headless e-commerce)

As a team, we used to build headless e-commerce using Apollo GraphQL. The setup is a bit tedious (download the schema.graphql using rover, add codegen for types, create fragments...).

Migrating to hydrogen-react should improve those (less setup). But the migration needs a lot of refactoring as I find myself often wanting to await the GraphQL query, as I used to do before.

I'd love the useCart() to return promises instead, would that be something you would consider?

This was mentioned in a previous issue, without much decisions. #685

Would be willing to help,
Thanks.

Which package or tool is having this issue?

hydrogen-react

What version of that package or tool are you using?

2023.4.5

[github-actions]

This issue has been marked as stale due to inactivity for 60 days. Please comment or update if this is still relevant, otherwise it will be closed in 7 days.

[pnodet]

😪

[github-actions]

This issue has been marked as stale due to inactivity for 60 days. Please comment or update if this is still relevant, otherwise it will be closed in 7 days.

[pnodet]

🥲

[stevenespinal]

I'm also running into this limitation with useCart(). I've observed a significant performance improvement when using @shopify/hydrogen-react over the traditional useOptimistic version, specifically on low tier network devices, where the useCart hook adds line items immediately (<300ms). Of course useOptimistic version renders the item immediately but the line item does not finish adding and the price does not show until 5 - 10 seconds later on low tier network devices.

Unfortunately, before I can fully commit to this approach, I need to resolve a blocking issue: our cart attributes are dependent on the newly added line items, and I'm unable to successfully call both linesAdd and cartAttributesUpdate sequentially. Currently, only the first mutation executes, and the second is silently ignored.

I haven't yet found a clean workaround that doesn't require modifying other independent processes that utilize cart level attributes. Any guidance on handling chained cart mutations or support for batching operations atomically would be greatly appreciated.