Storefront Next Release Notes

Learn about Storefront Next features that are part of the Storefront Next monthly releases.

To check out detailed changes in Storefront Next releases, see the releases page in the storefront-next-template GitHub repository. The changes listed in the releases page correspond to merged pull requests, which are the underlying changes of Storefront Next features.

Configure a shared parent cookie domain to keep shoppers logged-in with their baskets preserved when navigating between different subdomains. The domain-level cookie applies to storefronts that use multiple subdomains, such as www. and shop. on the example.com domain. It also applies to hybrid PWA Kit and SFRA storefronts that serve different paths under one parent domain. Without this configuration, shoppers lose their login status and shopping baskets when crossing subdomain boundaries. The loss of login status happens because browsers isolate cookies to individual hosts by default. Prevent frustration and abandoned carts by setting up domain-level cookies.

See Also

• Maintain Shopper Sessions Across Subdomains in Storefront Next

As part of upgrading your storefront to Storefront Next 1.1, you must upgrade React Router 7.12 to 7.18. React Router 7.18 provides improved security and stabilized APIs. It fixes an unauthenticated remote-code-execution vulnerability plus four additional security advisories in the turbo-stream dependency. The upgrade replaces several unstable_* API symbols with their stable counterparts, reducing breaking changes in future updates. Pin React Router and every @react-router/* package to 7.18.0 in package.json to prevent using an untested patch. Use the migration guide to perform the upgrade.

Where: This change applies to Storefront Next storefronts that use React Router 7.12 or earlier.

Why: The migration guide organizes the eight API stabilizations by how they surface—silent failures, typecheck-caught issues, and prefix swaps—so you can address high-risk changes first. For instance, the unstable_instrumentations export rename is silent at compile time but causes OpenTelemetry spans to fail at runtime if missed. The guide flags this upfront. You also get fixes for two React Router 7.16+ behavioral changes: an MRT streaming-drain issue that caused long responses to hang, and a fetcher idle-race condition that prevented checkout actions from firing. Both fixes ship in the SDK, so most projects inherit them automatically.

How: To learn more about the migration steps, check out Migrating to React Router 7.18 in the storefront-next-template GitHub repository. The migration guide includes step-by-step instructions, a Claude Code integration, code examples for each rename, and a verification checklist. To automate the migration, paste the guide into a Claude Code session with the framing prompt provided in the “7. Using this guide with Claude Code” section. Claude Code drives the entire rename set while skipping changes your project doesn’t need, such as SDK-internal fixes or test-only updates. After the migration, run the verification checklist to confirm all packages pin exactly to 7.18, typechecking passes, and no instrumentation warnings appear in your dev log.