[domiebett]

Adds an e2e check that a server-rendered Flex page prints one well-formed import map, ahead of every module, and that the embed hydrates. Until now only the import-map helpers had PHP unit tests; nothing checked the rendered page.

What changed

• New test Flex SSR published page in flex-and-ssr.spec.ts, run as a logged-out reader on a published post with a Flex SSR block. It checks that:
  • the page has exactly one import map (Firefox honours only a page's first map, so a second one breaks module resolution there);
  • the map comes before every module script and module preload;
  • the map carries every specifier in the experience's manifest, each with its integrity hash;
  • the embed hydrates (data-flex-ready) with no page errors. This experience does not load a mapped module while hydrating, so this does not show that the map resolves.
• The test fails when the experience's manifest has no imports or hashes, since the checks above would then pass without testing anything.
• PublishedPostPage gains importMaps, importMap() and modulesBeforeImportMap(); FlexRender gains ssrHydrated.

Running

• Locally against latest: the new test passes 3/3, and the Flex published render tests pass.
• The test fails when the renderer is broken in each of these ways (each change reverted after):
  • printing its own map instead of joining WordPress's (2 maps);
  • not registering the experience's specifiers;
  • not carrying the integrity hashes;
  • not printing the hydration script.
• With WordPress 6.9 and a block theme, WordPress prints the map in wp_head, so the footer hoist used for classic themes is not exercised here.

[github-actions]

✅ WordPress Plugin Check Report

✅ Status: Passed

📊 Report

All checks passed! No errors or warnings found.

---

🤖 Generated by WordPress Plugin Check Action • Learn more about Plugin Check

[Cporter97]

Looks good