Playbook · Hydrogen Vite plugin metafield missing
Shopify Hydrogen Vite plugin metafield missing? Prove plugin config, codegen, and Storefront selection.
Written for a Shopify owner whose Hydrogen Vite plugin / GraphQL codegen omits a metafield so the route payload never includes namespace.key. Start with vite.config Hydrogen plugin options, generated fragments, and Storefront access—not with a full Oxygen redeploy. This is distinct from Hydrogen React metafield blank (package render), from Hydrogen metafield blank (Remix loaders), and from Hydrogen storefront blank or error.
Nico at Latch AI Ops · Sep 17, 2026 · ~10 minute read
01
A missing Vite-plugin metafield is not the same bug as a blank Hydrogen React render.
Use this page when Hydrogen builds via the Vite plugin (or companion GraphQL codegen) and the generated query/fragment never selects the metafield, so the field is absent from the payload before JSX runs. If the client JSON includes the field but the UI stays blank, use Hydrogen React metafield blank. If the whole Oxygen deploy is white, use Hydrogen storefront blank or error.
Capture Vite plugin version, Hydrogen version, Storefront API version, generated fragment path, and namespace.key before changing tokens.
02
Prove Vite plugin config and generated fragment fields.
Open vite.config.ts (or .js) and record Hydrogen plugin options, especially codegen / graphql paths. Inspect the generated Product, Variant, Cart, or Shop fragment under storefrontapi.generated.d.ts or your project's codegen output.
If the fragment omits metafield / metafields, regenerate after adding the selection—do not assume a runtime cache wipe will invent fields the plugin never emitted.
03
Check Storefront selection, namespace.key, and access.
Confirm the route loader or client query uses the regenerated fragment and the exact namespace.key from Admin. A product fragment will not return variant-owned values. Soft-link Storefront API version metafield missing when the API version header predates a field or type you need.
Confirm Storefront access on the definition and that the Storefront token can read that owner. Keep private tokens out of client bundles and screenshots.
04
Confirm one known Admin value before blaming Oxygen or CDN cache.
In Admin Custom data, save a short reversible test value on the same owner and confirm it survives. Hit Storefront API (or Hydrogen debug) for that handle and verify whether the field is omitted, null, or present.
Classify: plugin/codegen omit, wrong selection, storefront access off, empty Admin value, or stale build artifact. Those are different failures.
05
Retest one route and keep a small proof packet.
Use one product (or cart) route, one Vite rebuild, and one known owner. Record plugin config, generated fragment snippet, namespace.key, Admin value, storefront access, raw Storefront JSON, and Hydrogen payload. Redeploy Oxygen only after that packet exists.
Keep the miss separate from Hydrogen React render blanks, Remix loader blanks, and Oxygen blank deploys so the next codegen change stays reversible.
06
When to stay DIY vs pay $997.
Stay DIY when one plugin config, fragment, access, or selection check explains the missing field. Keep the proof packet so future Hydrogen upgrades stay grounded.
Pay for the $997 one-time install when several Shopify surfaces, headless apps, and ops alerts need to be wired and documented on one live store. Nico at Latch AI Ops can connect the agreed workflow in a 72-hour window after collaborator access. No earnings claim, conversion guarantee, or theme rebuild is included; owner passwords are not requested.