Hydrogen 2026‑10 Goes GA: Add Shopify Commerce to Any JavaScript Framework

Hydrogen 2026‑10 is now generally available, turning the once‑exclusive React‑only framework into a universal library you can drop into any JS stack. Learn what changed, who it impacts, and how to upgrade or start fresh.

Hydrogen 2026‑10 Goes GA: Add Shopify Commerce to Any JavaScript Framework
6 sections

Shopify’s Hydrogen library has reached a major milestone: version 2026‑10 is now generally available. After a developer preview that shipped seven incremental releases, Hydrogen has transformed from a React‑only framework into a framework‑agnostic library you can plug into any JavaScript stack. This post breaks down the new capabilities, who needs to pay attention, and the exact steps you should take to adopt or migrate your storefront.

What’s New in Hydrogen 2026‑10

  • Framework‑agnostic library – Hydrogen is no longer a full‑stack framework built on React Router. It’s now a lightweight library you import into React, Vue, Next.js, Remix, Svelte, or any other JS framework. Your existing routing, data fetching, and rendering stay exactly as they are.
  • Zero‑code commerce primitives – The library still provides out‑of‑the‑box cart handling, variant selection, price localization, analytics consent, Shop Pay, and customer authentication. All the heavy lifting is abstracted behind a few hooks or composables.
  • Starter templates for React Router & Next.js – Deployable starter projects live on Oxygen (still free) and Vercel, giving you a quick launchpad if you prefer a conventional framework setup.
  • Built‑in “skills” for coding agents – 20 pre‑written agent skills can scaffold a full storefront, add analytics, and even run smoke tests. Sync them with npx @shopify/hydrogen skills sync after each version bump.
  • Compatibility with Shopping Agents – Stores built with the new library work seamlessly with WebMCP‑enabled shopping agents, allowing AI‑driven search and cart updates without extra code.
  • Who Is Affected?

  • Developers – If you’ve been building custom storefronts, you can now keep your favorite framework and simply add Hydrogen’s commerce layer. Existing Hydrogen‑React projects continue to run unchanged, but you’re encouraged to try the migration skill when ready.
  • Merchants with custom storefronts – No immediate action is required. Their current Hydrogen sites keep working. However, they gain a path to faster iterations and lower hosting costs by moving to a framework they already manage.
  • App developers & partners – Because Hydrogen now uses the same standard storefront actions as Liquid themes, existing cart‑related apps can interact with Hydrogen stores without code changes (e.g., window.Shopify.actions.updateCart).
  • How to Add Hydrogen to an Existing Project

    Open a terminal in your project folder and run:

    bash

    npx @shopify/hydrogen@latest setup

    The command installs the @shopify/hydrogen package, adds a default hydrogen.config.ts (or .js) file, and injects a minimal provider component you can wrap around your app.

    Example for a React app:

    tsx

    import {createCartComponents, HydrogenProvider} from "@shopify/hydrogen/react";

    const {CartProvider, useCart} = createCartComponents();

    function App() {

    return (

    <HydrogenProvider shop="my‑store.myshopify.com" language="en" country="US">

    <CartProvider>

    {/* Your routing / UI components */}

    </CartProvider>

    </HydrogenProvider>

    );

    }

    Vue composable equivalent:

    ts

    import { useCart } from "@shopify/hydrogen/vue";

    export default {

    setup() {

    const { cart } = useCart();

    return { cart };

    }

    };

    After the provider is in place, you can call any of Hydrogen’s hooks/composables to render a cart count, fetch product data, or trigger checkout.

    Migrating from the Old Hydrogen Framework

    If you have a storefront built on the pre‑2026‑10 Hydrogen (React Router + built‑in routing), you don’t need to rush to change anything—everything continues to work. When you’re ready to switch:

  • Run the migration skill: npx @shopify/hydrogen skills run migration.
  • Replace the old <Router> import with your framework’s router (React Router, Next.js, etc.).
  • Keep your page components; only the commerce‑specific code moves from the framework into Hydrogen’s provider.
  • Deploy to your preferred host – Oxygen remains free for Hydrogen libraries, or push to Vercel, Netlify, Cloudflare, etc.
  • Action Items for Developers and Merchants

    Developers

  • Install the latest package (npx @shopify/hydrogen@latest setup).
  • Review the new hydrogen.config options (e.g., storeDomain, defaultCurrency, analyticsConsent).
  • Update any CI pipelines that assumed a full‑stack Hydrogen build; now you only need to bundle the library.
  • Merchants with custom storefronts

  • No immediate changes required; monitor the “Hydrogen” app section in the Shopify admin for new deployment options.
  • Consider a pilot project using the React Router starter on Oxygen to evaluate performance and hosting costs.
  • Conclusion & Next Steps

    Hydrogen 2026‑10 opens the door for any JavaScript team to bring Shopify’s commerce engine into their favorite framework without rewriting the entire storefront. Whether you’re a seasoned Hydrogen developer, a Vue or Svelte shop, or a merchant curious about a custom UI, the new library gives you the commerce building blocks and lets you focus on design and experience. Start experimenting today, sync the agent skills, and watch your storefront become more flexible, faster, and easier to maintain.

    Ready to upgrade? Run npx @shopify/hydrogen@latest setup in your repo, explore the starter templates, and join the conversation in the Shopify developer community for any questions.

    Tags
    Sources

    Related Articles

    Checkout Footer Visibility Update: What Merchants and Developers Need to Know

    Checkout Footer Visibility Update: What Merchants and Developers Need to Know

    Shopify now separates merchant‑configurable footer content from Shopify‑provided copy in the checkout. Learn how this change impacts your branding apps, what stays the same, and the actions you should take.

    October 15, 20263 min
    Shop MCP Unlocks In‑Agent Shopping and Shop Pay Checkout

    Shop MCP Unlocks In‑Agent Shopping and Shop Pay Checkout

    Shop MCP lets developers add full catalog search, cart creation, and Shop Pay checkout directly inside any agent. Learn what changed, who’s affected, and how to start using the new tools today.

    October 13, 20265 min
    Sidekick Empowers Merchants to Customize Checkout and Account Settings Directly

    Sidekick Empowers Merchants to Customize Checkout and Account Settings Directly

    Shopify’s Sidekick is now integrated into the checkout and accounts editor, giving merchants instant guidance, app recommendations, and configuration help. Learn what changed, who it impacts, and how to start using Sidekick today.

    October 13, 20264 min
    Why Unchanged Cart Updates No Longer Spam Your Carts/Update Webhooks (and What to Do)

    Why Unchanged Cart Updates No Longer Spam Your Carts/Update Webhooks (and What to Do)

    Shopify now suppresses carts/update webhooks when a cart operation makes no actual change. Learn what this means for your apps, how to adjust your webhook logic, and best practices to keep your integrations lean and reliable.

    October 12, 20264 min