$ the-wire · showcase
Hydrogen fixes hydration interruption, Shopify CLI adds --no-input
By RepoJournal · Filed · About Shopify · Composed from the cited sources · methodology
Hydrogen's patch train lands a React hydration fix in the analytics provider and an env-pull correctness fix, while the CLI makes interactive behavior switchable for scripts and agents.
@shopify/hydrogen@2026.4.7 Shopify/hydrogen
Deferred cart, shop, and consent state updates now run inside startTransition, so React no longer abandons server-rendered HTML while Suspense boundaries are still dehydrating. useAnalytics().publish also stops emitting the state update when consent changes underneath it.
@shopify/cli-hydrogen@13.0.6 Shopify/hydrogen
h2 env pull no longer corrupts values containing backslashes, double quotes, or tabs: they are single-quoted where possible so dotenv reads them back exactly, and $ and backticks survive a shell sourcing the .env.
Add `--no-input` to all commands Shopify/cli
A global --no-input flag joins the existing globals and disables prompts, browser launches, keypress handling, and REPL input while keeping piped input working. Required input that is unavailable now surfaces an actionable error, which is what scripted and agent-driven runs needed.
@shopify/create-hydrogen@5.0.40 Shopify/hydrogen
--template skeleton on h2 init and npm create @shopify/hydrogen now behaves like omitting the flag: dependencies install, .env and the project name are set up, and every other flag is honored instead of downloading GitHub's latest release. Non-interactive runs using it should pass the same prompt-skipping flags as the default init flow, --mock-shop, --markets, and --styling among them.
Add `shopify app import channel-config` for partner channel spec import Shopify/cli
shopify app import channel-config gives legacy channel apps a partner-owned, deployable copy of the public parts of the channel_config extension spec, replacing reliance on app-level FrozenRecord fallback specs. Forked PRs remain unsupported for /snapit snapshot publishing, which now dispatches a separate release run on the default branch since npm blocked Trusted Publishing from issue_comment ...
