Skip to content
On this page

Changelog

From 4.0.0 on, the framework and the storefront each release all their packages under one version. Before 4.0, packages were independently versioned; that history is kept below. Features rarely live in just one package: a cacheable checkout is a core flag, a compatibility module and a theme template landing together. This page follows the stack, so you can read what changed without having to recompose it from a dozen release feeds.

Each entry names the packages and versions that carry it. For the commit-level history of a single package, see its releases on GitHub.


Storefront 4.3.2 — 2026-11-10

A checkout fix. The framework and theme-default do not change, and no theme rebuild is needed.

Fixed

  • module-checkout — with terms and conditions enabled (checkout/options/enable_agreements), a manual agreement showed on the one-page checkout as plain text, without its checkbox, and Place order stayed enabled. The server still requires every manual agreement, so each order was refused with "The order wasn't placed. First, agree to the terms and conditions, then try placing your order again." and the customer had no way to accept them. Magento reads the agreement mode from the database as text, and the checkout compared it with a number. The checkbox is back, and Place order waits for it. The multi-address checkout was not affected.

Upgrade notes

  • Run composer update mage-obsidian/* and bin/magento cache:flush: the checkout's configuration is part of the cached page.

Storefront 4.3.1 — 2026-11-09

Security fixes. The framework and theme-default do not change, and no theme rebuild is needed.

Fixed

  • module-checkout, module-wishlist — the full-page cache could store the pages that edit a cart item (checkout/cart/configure) and a wish list item (wishlist/index/configure). They show the options, text and quantity one customer chose, so a second visitor asking for the same URL could be served them. Both pages are now uncacheable, whatever the Varnish or Fastly configuration.
  • module-send-friend — the "Email to a Friend" form was cacheable, and it fills the sender with the signed-in customer's name and email. It is now uncacheable, as in Magento's own layout.
  • module-search, module-checkout, module-customer, module-catalog — five request parameters answered with a 500 error, without signing in, when they arrived as an array, for example ?obsidian_fragment[]=1: obsidian_fragment and obsidian_data on listings, obsidian_shell on the checkout, referer on the sign-in and account creation pages, and ids on the recently viewed products endpoint. An array is now treated as if the parameter were absent.

Upgrade notes

  • Run composer update mage-obsidian/* and bin/magento cache:flush.
  • Purge from Varnish or Fastly the cart and wish list edit pages and the "Email to a Friend" pages it already holds: a copy stored before the upgrade is served until it expires.

Framework 4.3.0 and storefront 4.3.0 — 2026-11-02

Under a MageObsidian theme the storefront's Content Security Policy now enforces, with MageObsidian's recommended policy on top: a hand-written inline script, an on*= attribute in markup or an eval stops running. Check the storefront in staging before upgrading. To keep the previous behaviour, a module turns the recommended policy off through DI: MageObsidian\ModernFrontend\Service\Csp\RecommendedPolicy, argument enabled set to false.

Added

  • module-modern-frontend — a recommended policy, on by default: enforce mode, no 'unsafe-eval', no 'unsafe-inline' in script-src, style-src or default-src, and base-uri 'self' and object-src 'none'. It applies on top of the final policy, including what modules add while the page renders, and stays in report-only while the Vite dev server is on. No admin setting turns it off.
  • module-modern-frontend — on a response the full-page cache may store, inline scripts are authorized by the sha256 of their content instead of a nonce. Under Varnish or Fastly, a cached page no longer shares one nonce with every visitor. Third-party modules that emit their scripts through SecureHtmlRenderer are covered without changes.
  • module-modern-frontend — Magento's built-in page cache stores, with each entry, the authorizations the page collected while it rendered, and puts them back on every hit. A page served from it no longer blocks its own scripts.

Changed

  • module-modern-frontend — the runtime configuration (translations, section data, UX flags, icon base, pre-paint, section prefetch) travels as <script type="application/json" data-mage-obsidian-config="…"> data blocks instead of inline scripts that set window.__MAGE_OBSIDIAN_*__. The browser does not execute them, so the policy has nothing to authorize. The contract schema moves to 1.2.0.
  • module-modern-frontend — the checkout and the multi-address billing step no longer allow inline styles. The styles the storefront emits there are authorized by hash. A module that needs the exception declares the page through DI; no store configuration allows inline styles on a page the code did not declare.
  • module-storefront — the password visibility toggle reads its icons with readPageConfig().

Fixed

  • module-modern-frontend — a page served from Magento's built-in page cache went out with the platform's default policy (report-only, with 'unsafe-inline') instead of MageObsidian's. On a cache hit Magento loads no theme, so the theme detector answered "not a MageObsidian theme". When no theme has been loaded yet on the storefront, the detector now uses the theme configured for the store view. The strict inline policy of 4.1.3 had the same gap.

Upgrade notes

  • Update the framework and the storefront together, and rebuild every theme. Composer enforces it: module-modern-frontend 4.3 conflicts with module-storefront and component-modern-frontend releases before 4.3. The 4.3 harness installs engine 4.2.0, the first that reads contract 1.2.0. An older engine in vite/ fails the build with Schema version mismatch, on purpose: a theme built by it would render pages without translations or section data.
  • After deploying, run bin/magento cache:clean full_page block_html, and purge Varnish or Fastly. Pages and blocks cached before the upgrade carry a nonce in their HTML. Under the built-in page cache, entries stored before the upgrade are rendered again on their own.
  • Place a test order with every payment method the store runs. A payment method that injects its own <style> element is blocked; the payment pages section explains the options.
  • Code that reads window.__MAGE_OBSIDIAN_*__ keeps finding them once the runtime has started. Code that runs before it reads the data block with readPageConfig().
  • A store that had set report-only on purpose gets enforce with this release. Turning the recommended policy off through DI brings back the mode its configuration asks for.
  • To roll back, go back to the previous release and run bin/magento cache:clean full_page.

Framework 4.2.0 — 2026-11-02

Engine only. It prepares the runtime for the data blocks of 4.3.0 and changes nothing on a store that stays on this release.

Added

  • js-package-utils — mage-obsidian/runtime/pageConfig.ts, with readPageConfig(), to read the configuration the server hands to the runtime. It reads the data-mage-obsidian-config data block and, on a server from before the data blocks, falls back to window.__MAGE_OBSIDIAN_*__.
  • js-package-utils — the build engine accepts contract 1.2.0.

Upgrade notes

Nothing to do. The PHP packages are the 4.1.4 ones apart from their version.


Framework 4.1.4 — 2026-10-25

Fixed

  • module-modern-frontend — on Magento Open Source 2.4.7 without patches, every storefront page rendered with an empty body: no header, content or footer. Since 4.1.0 the framework asked Magento for its list of payment pages through a class that magento/module-csp only ships from a later 2.4.7 patch on, and the page failed to build without it. The framework now reads that list from Magento when Magento has it, as before, and otherwise uses its own: the checkout, the order confirmation and the multi-address billing step. Scripts on those pages keep their subresource integrity hashes in both cases.

Upgrade notes

Nothing changes on Magento 2.4.8 or later, on Mage-OS, or on a patched 2.4.7. On a 2.4.7 store, run bin/magento setup:di:compile after updating, as for any framework release.


Framework 4.1.3 and storefront 4.2.1 — 2026-10-25

In a store whose store views use different themes, MageObsidian now acts only in the store views whose theme is a MageObsidian theme. A store view on any other theme gets Magento's own behaviour, as if MageObsidian were not installed. Store views on a MageObsidian theme do not change.

Changed

  • module-modern-frontend — the strict Content Security Policy, where an inline script or style runs only with a nonce or a hash, is applied while the request runs and only under a MageObsidian theme. config.xml no longer sets csp/policies/storefront/scripts/inline or csp/policies/storefront/styles/inline. The checkout and the multi-address billing step keep inline styles, as before, unless the store configured those pages itself.

Fixed

  • Widgets (module-catalog, module-sales) — under another theme, the product list, new products, recently viewed, recently compared and orders and returns widgets keep Magento's templates. They used to switch to templates only a MageObsidian theme has, and rendered empty.
  • CMS content (module-storefront) — under another theme, pages and blocks are no longer wrapped in div.cms-content, and Page Builder content leaves the filter as Magento wrote it: no styles handed over for hashing, no image dimensions added, no behaviour scripts. That includes the emails those store views send.
  • Head metadata (module-storefront) — under another theme, the meta description is not derived, robots is not extended and no social metadata is added.
  • Showcase (module-showcase) — a demo profile a visitor brings from another store view of the same domain changes nothing under another theme: no configuration override, no cache variation, no telemetry.

Upgrade notes

Only a store with a store view on a theme that is not a MageObsidian theme sees a difference. In those store views, after the next cache:flush:

  • widgets, CMS content and the <head> render as Magento renders them;
  • the Content Security Policy is the one Magento and the store's own configuration produce. To keep those store views as strict as before, set csp/policies/storefront/scripts/inline and csp/policies/storefront/styles/inline to 0 for their website. config:set rejects these paths, because Magento_Csp does not declare them in system.xml; write them in the system section of app/etc/env.php or app/etc/config.php instead.

A store view counts as a MageObsidian store view when its theme is in the contract. A theme that inherits from MageObsidian/default has to ship its own etc/mage_obsidian_compatibility.xml; inheriting is not enough. To check:

bin/magento mage-obsidian:frontend:config --show --themes
bin/magento mage-obsidian:frontend:doctor

The first lists the themes in the contract. In the second, a Contract drift warning means the contract is older than the enabled themes; bin/magento mage-obsidian:frontend:config --generate regenerates it, and so does every static content deploy.


Framework 4.1.2 — 2026-10-15

Fixed

  • module-modern-frontend — a cached block keeps only the Content Security Policy hashes of the inline styles and scripts it rendered itself, its children's included. Magento's block cache stored every hash collected in the request up to that block and restored them on every hit, so on a listing with layered navigation the style-src list grew with each filter combination visited, until the response header outgrew the web server's buffer and the page answered 502.

Upgrade notes

The fix replaces Magento\Csp\Model\BlockCache through a preference. If another module also prefers that class, only one of the two applies.

Blocks cached before the upgrade still carry the hashes they accumulated. Clean the block cache once after deploying:

bin/magento cache:clean block_html

Storefront 4.2.0 and theme-default 4.2.0 — 2026-10-15

theme-default 4.2.0 requires storefront ^4.2: its product page relies on styles that ship in module-storefront 4.2.0. Upgrade them together.

Added

  • Compare and wish list buttons (module-storefront) — they show progress while the request runs: a ring around the round buttons on product cards, and a spinner in place of the icon on wider buttons. Under reduced motion the indicator stays still.
  • Product page (theme-default) — wish list and compare are two buttons side by side under add to cart, and read "Remove from Wish List" and "Remove from Compare" once the product is in the list. The price alert, stock alert and email to a friend links stand in a list of their own.
  • Compare page (theme-default) — each product shows its image with a remove button over it, then add to cart or choose options, and the wish list as an icon.

Fixed

  • Listings (module-storefront) — on cards that a filter, sort or page change swaps in, the compare and wish list buttons show whether the product is already in the list. Before, they looked unpressed, and pressing one removed the product.
  • Catalog (module-catalog) — the round compare button of a compared product fills with the accent color and keeps its icon visible.
  • Forms (module-storefront) — selects draw their own chevron with room from the border, so the selected text no longer runs into it.
  • Wish list (theme-default, module-wishlist) — remove and edit sit over the image as icons, quantity and add to cart share one row that wraps on narrow cards, and the note field is compact.
  • Header (theme-default) — the pinned bar blurs the page scrolling under it again. Since 4.1.0 the content showed through it sharply, because the name the header carries for page transitions kept the blur from reaching the page; the header now carries it only while a transition runs.
  • Search (theme-default) — the related search terms no longer sit between two rules.

Upgrade notes

Regenerate the critical CSS after upgrading. The inlined copy keeps the header rule from 4.1.0, and with it the header stays without blur until it is regenerated:

bin/magento mage-obsidian:frontend:critical-css --handle=catalog_category_view

Repeat it for every handle you generate critical CSS for; see Generating the critical CSS.


Framework 4.1.1 — 2026-10-13

Changed

  • component-modern-frontend — the Vite harness requires engine ^4.1.0, so builds get the engine changes of 4.1.0 below.

Upgrade notes

Install 4.1.1, not 4.1.0 alone. The scripts that module-modern-frontend 4.1.0 ships import runtime modules that only exist from engine 4.1.0 on, and the 4.1.0 harness still installs engine 4.0.1, so a theme build with it fails on the import.

Engine 4.1.0 was published on 2026-10-13 at 13:38 UTC. Until 2026-10-14 at 13:38 UTC, pnpm 11 refuses it under minimumReleaseAge. Either wait, or exempt that one version for the install:

pnpm_config_minimum_release_age_exclude='["mage-obsidian@4.1.0"]' pnpm install --frozen-lockfile

Framework 4.1.0 — 2026-10-13

Added

  • js-package-utils (mage-obsidian on npm) — the build writes a sha384 integrity hash for every chunk into the Vite manifest.
  • module-modern-frontend — on the checkout, the order confirmation and the billing step of multi-address checkout, module scripts, modulepreload links and the import map carry integrity and crossorigin. See Subresource Integrity on payment pages.
  • module-modern-frontend — setup:static-content:deploy checks every published script against its manifest hash and warns about the ones that differ, since browsers would refuse to run them on payment pages; with MAGE_OBSIDIAN_STRICT_DEPLOY=1 it fails the deploy.
  • js-package-utils — cookies written by the storefront runtime use the path, domain, lifetime and Secure flag the store publishes, instead of fixed values.

Fixed

  • js-package-utils, module-modern-frontend — cached private sections are scoped to the website, store view and currency that produced them. A cache produced by another scope, or stored before scoping existed, is dropped instead of shown.
  • js-package-utils — clearing a cookie also clears its host-only variant, and the session marker cookie stays host-only.
  • module-modern-frontend, module-modern-frontend-twig — where the page's style-src allows inline styles, the style Twig tag and the critical CSS are delivered from a nonced script that adopts them as a stylesheet.
  • module-modern-frontend-twig — the number filter returns a non-numeric value unchanged instead of formatting it.
  • js-package-utils — a theme without web/theme.config.js builds as if it had an empty one and inherits its parents' values. Until 4.0.2 the build stopped with Cannot read properties of null (reading 'ignoredCssFromModules').

Upgrade notes

Superseded by 4.1.1; see above.


Storefront 4.1.0 and theme-default 4.1.0 — 2026-10-13

The storefront packages require framework ^4.1, and theme-default requires storefront ^4.1. Upgrade them together.

Added

  • Store configuration followed — configured customer attributes, address fields and password policy in the account and checkout forms; tax display settings for cart, checkout and product prices; mini cart display limits and the redirect to the cart; layered navigation counts, search length, send-to-friend recipients and other catalog limits; links to features the store disabled are hidden.
  • Checkout and cart — saved billing addresses, offline payment instructions and the purchase order number, cart validation and line messages, a paged cart, cross-sells that add to the bag, wish list and compare, a carrier renderer extension point, and print, downloads and an account offer on the success page.
  • In-store pickup — new package module-inventory-in-store-pickup: a delivery method selector and a pickup location finder over the MSI pickup endpoints. See In-store pickup.
  • CAPTCHA and reCAPTCHA — the login CAPTCHA once failed attempts require it, and reCAPTCHA on the cart coupon form and the wish list share form.
  • Catalog — configurable swatches on listing cards, with the complete variant priced and added from the card; the category image; tier prices, quantity increments and stock on the product page; a click-to-load facade for provider videos; search suggestions; product views and search terms recorded from cached pages; new, recently viewed and recently compared product widgets.
  • Account and sales — saved wish list options, ratings, notes and quantity updates; comments, status, print, reorder and tracking on order documents; bundle, downloadable and fixed tax lines in order emails; the recently ordered sidebar and the orders and returns widget.
  • Storefront chrome — store group switcher, configured logo, welcome message and copyright; compare and wish list sidebars; account entry points in the mobile menu; Google Ads tags and conversion reporting; RSS feed discovery and links; stock alert unsubscribe from the email link; full-bleed Page Builder rows; the persistent cart greeting with "not you?".
  • Security — the storefront's own scripts carry Subresource Integrity on payment pages, with framework 4.1.

Fixed

  • Checkout — a guest whose email already has an account is offered to sign in and can still continue as a guest, as on Luma. It was blocked before.
  • Wish list — sharing sends the wish list being viewed instead of the default one.
  • Catalog — product cards in a row share one height, with their actions aligned at the bottom.
  • Header — the main bar stays pinned at the top while scrolling.
  • Cached pages — the site config publishes the store view and currency, so cached sections from another store view or currency are not shown.

Framework 4.0.2 — 2026-10-07

Changed

  • component-modern-frontend — the Vite harness requires engine ^4.0.1 and Vue ^3.5.42. Builds now get the two engine fixes from 4.0.1: a child theme inherits its parents' theme.config.js values, and the ancestor CSS sources stop at includeCssSourceFromParentThemes: false.

Security

  • component-modern-frontend — the harness lockfile resolves @vue/server-renderer 3.5.43, source-map-js 1.2.2 and brace-expansion 2.1.7, which close the advisories open against the harness.

Upgrade notes

Run composer update 'mage-obsidian/*', then pnpm install in vite/. mage-obsidian 4.0.2 on npm carries the same engine code as 4.0.1; only its development tooling changed.


Framework 4.0.1 — 2026-10-06

Fixed

  • js-package-utils (mage-obsidian on npm) — a child theme inherits its parents' theme.config.js values. The defaults are applied after the merge, so a parent's vue.runtimeOnly: true or ignoredCssFromModules: "all" is no longer reset in the child.
  • js-package-utils — the ancestor themes' CSS sources stop at the nearest ancestor that sets includeCssSourceFromParentThemes: false, instead of always reaching the root theme.
  • module-modern-frontend — a contract regenerated with mage-obsidian:frontend:config --generate takes effect without reloading PHP-FPM, also with opcache.validate_timestamps=0.
  • module-modern-frontend-cli — mage-obsidian:generate:theme writes includeCssSourceFromParentThemes, the key the engine reads, instead of includeParentThemes, which nothing read.

Upgrade notes

^4.0 already resolves the PHP packages to 4.0.1. The Vite harness still installs engine 3.2, so the two engine fixes reach a build once the harness requires engine 4.0.1.


Storefront 4.0.1 — 2026-10-06

Fixed

  • theme-base — nine templates failed with a fatal error on PHP 8.3 and 8.4, because the license header sat in a closed PHP block before declare(strict_types=1).
  • theme-base — root.phtml read $headAssets, which Magento 2.4.7 never assigns, so every page returned HTTP 500 on 2.4.7.

Upgrade notes

Nothing to do: ^4.0 already resolves to 4.0.1.


4.0.0 — 2026-10-06

Highlights

  • Stable. 4.0.0 is the first stable release of the monorepo era.
  • Two release trains. The framework and the storefront each release all their packages under one version.
  • Monorepos. The framework and the storefront now live in one repository each.

Upgrade notes

See the upgrade guide from 3.x to 4.0.

Deprecated

Nothing.

Version map

Last version of each package before 4.0, and the 4.0.0 release.

Package Last before 4.0 4.0.0
mage-obsidian/module-modern-frontend 2.22.0 4.0.0
mage-obsidian/module-modern-frontend-cli 2.9.0 4.0.0
mage-obsidian/module-modern-frontend-twig 2.7.1 4.0.0
mage-obsidian/component-modern-frontend 2.7.0 4.0.0
mage-obsidian (npm) 3.2.0 4.0.0
mage-obsidian/module-catalog 3.12.0 4.0.0
mage-obsidian/module-catalog-search 2.2.0 4.0.0
mage-obsidian/module-checkout 3.12.1 4.0.0
mage-obsidian/module-customer 2.4.1 4.0.0
mage-obsidian/module-downloadable 2.2.0 4.0.0
mage-obsidian/module-gift-message 2.2.0 4.0.0
mage-obsidian/module-instant-purchase 2.2.0 4.0.0
mage-obsidian/module-multishipping 2.1.0 4.0.0
mage-obsidian/module-persistent 2.1.0 4.0.0
mage-obsidian/module-product-alert 2.1.0 4.0.0
mage-obsidian/module-review 2.3.0 4.0.0
mage-obsidian/module-sales 2.4.0 4.0.0
mage-obsidian/module-search 1.3.0 4.0.0
mage-obsidian/module-send-friend 2.2.0 4.0.0
mage-obsidian/module-showcase 1.5.0 4.0.0
mage-obsidian/module-storefront 3.23.0 4.0.0
mage-obsidian/module-vault 2.3.0 4.0.0
mage-obsidian/module-wishlist 2.3.0 4.0.0
mage-obsidian/theme-base 3.13.1 4.0.0
mage-obsidian/theme-default 3.21.3 4.0.0

Before 4.0

Where this starts

The whole stack was cut to 2.0.0 together on 22 June 2026, and that is where this log begins. Anything older predates the current line.


September 2026

Following a link inside the store no longer flashes a blank screen or a header over an empty body on a slow phone. The previous page stays on screen until the next one has parsed its main content, and a thin progress bar and a screen-reader announcement acknowledge the click at once. First visits, arrivals from other sites and reloads still paint progressively, so first-load metrics do not move. See Navigation continuity.

  • module-storefront 3.23.0 — hold the previous page until the next has its main content (mage_obsidian/navigation/retain, on by default); click progress indicator; requires core ^2.22
  • module-modern-frontend 2.22.0 — inlined head scripts are printed without their source file's license header (RuntimeScriptReader)
  • module-modern-frontend-twig 2.7.1 — inline_view_file drops a view file's license header
  • theme-default 3.21.3 — translation of the progress announcement

Builds without a database

A store can now build MageObsidian in a phase with no database and under another root path, then deploy the result: the model of Adobe Commerce Cloud and of any pipeline that ships an artifact. Static deploy regenerates the frontend contract from the filesystem, with paths relative to the Magento root, and the Vite build can be skipped, checks it can write before emptying anything, and honours theme exclusions. See Adobe Commerce.

  • mage-obsidian 3.2.0 — resolve contract paths against the Magento root; accept schema 1.1.0; MAGE_OBSIDIAN_BUILD_CONCURRENCY
  • component-modern-frontend 2.7.0 — require engine ^3.2.0
  • module-modern-frontend 2.21.0 — themes read from the filesystem; contract regenerated in static deploy with root-relative paths (schema 1.1.0); MAGE_OBSIDIAN_SKIP_VITE_BUILD, write checks and theme exclusions in the Vite build; critical CSS read from web/critical/; CMS baseline status per theme
  • module-modern-frontend-cli 2.9.0 — critical CSS written to <theme>/web/critical/ with relative font URLs, which the core resolves for the serving store; CMS baseline row in the doctor; requires core ^2.21

Upgrading: regenerate each theme's critical CSS after upgrading; the old file under web/generated/critical/ is dropped by the next Vite build.

Guest checkout that asks to sign in, and messages that repeat

With a downloadable product in the bag, Magento refuses guest checkout by default. Natively the checkout buttons ask the guest to sign in; ours navigated to /checkout, which bounced back to the cart, and the "Guest checkout is disabled." message showed only on the first try. The buttons now send the guest to sign in with a referer back to checkout, the sign-in page returns there, and a session message the server sends again always shows.

  • module-checkout 3.12.1 — the cart page and mini-cart checkout buttons lead a guest to sign in when the cart refuses guest checkout
  • module-customer 2.4.1 — a sign-in that carries a referer returns to it
  • module-storefront 3.22.1 — show a repeated session message when its cookie was cleared
  • theme-default 3.21.2 — pass the sign-in URL to the checkout buttons

Installs that hold up outside our environment

Fixes found installing the stack on a store it was not built on: defaults that only worked in our own environment, checks that failed a healthy deploy, and a policy that blocked payment pages.

A fresh install serves built assets. module-modern-frontend shipped HMR switched on, and Magento only overrides that flag in production mode, so a new store in the default mode asked a Vite dev server that was not running for every asset: all of them returned 404 and no island mounted. HMR is now off by default and opt-in. mage-obsidian:frontend:hmr --enable and mage-obsidian:frontend:dev --up still turn it on. If you use the dev server and never saved the flag yourself, run bin/magento mage-obsidian:frontend:hmr --enable once after upgrading; the doctor reports "HMR disabled" until you do.

The doctor reports Adobe Commerce coverage. On an Adobe Commerce install, mage-obsidian:frontend:doctor adds a section listing the Commerce-only storefront families, the Commerce modules behind each one and whether a MageObsidian module covers it.

A production build no longer asks for dev server settings. mage-obsidian 3.1.0 validates the dev server variables only with --dev-server, and only VITE_SERVER_HOST and VITE_SERVER_PORT are required. Without a terminal it never prompts. Before, a build without vite/.env opened a prompt, exited 1 and aborted setup:static-content:deploy in any CI.

PHP 8.3 is required. Every MageObsidian Magento module now declares "php": ">=8.3", and module-modern-frontend requires Magento 2.4.7 or later. The code uses typed class constants, so on PHP 8.2 Composer installed the packages and setup:di:compile then failed with a parse error. PHP 8.2 is no longer supported.

A failed compile keeps the CMS delta you had. When the Tailwind binary was missing, timed out or failed, module-modern-frontend wrote an empty delta over the last good one, and the classes the build did not cover lost their styles until the next successful save. The previous stylesheet now stays in place. A compile that fails with the binary installed is logged; a missing binary is left to the doctor, which already reports it.

The frontend contract is regenerated only when the module list is written. Every write to config.php or env.php regenerated it, so a failure there broke deploy:mode:set and setup:config:set. It now runs only when the modules section is written, and a failure is logged with the command to run instead of failing the write. A contract that fails its schema no longer leaves the .php file rewritten either: both files are written only after validation passes.

Payment pages allow inline styles again, and the pre-paint survives a strict policy. Magento enforces the policy on checkout_index_index and multishipping_checkout_billing, and our storefront-wide styles/inline=0 blocked the inline styles payment extensions inject there. Both pages are back to Magento's default. The pre-paint now applies its rules through a constructable stylesheet, which style-src does not govern, and falls back to a <style> element only in browsers without them.

Static deploy reports themes with no Vite build. A theme whose build output was missing or empty passed the deploy in silence. It is now named in a warning. Set MAGE_OBSIDIAN_STRICT_DEPLOY=1 to turn that warning, and a failure to publish the build, into a failed deploy.

Source-writing commands refuse production mode. mage-obsidian:generate:module, :theme, :component and mage-obsidian:i18n:collect exit with an error in production mode instead of failing halfway through a write. mage-obsidian:frontend:dev is unchanged.

Page Builder classes stay out of the CMS delta. pagebuilder-* classes never resolve to a Tailwind rule and filled the delta's unresolved list. They are skipped by default; the prefix list is an ignoredClassPrefixes argument of ContentExporter in di.xml.

The Vite harness installs outside our own environment. component-modern-frontend shipped vite/pnpm-workspace.yaml with a pnpm store under /home/www and the supply-chain release-age check switched off, both settings of our local environment. On any machine where /home/www is not writable, pnpm install failed. Both are gone; if you relied on that store path, set pnpm_config_store_dir in your environment. The harness now declares engines.node >=22.13, the floor of the pnpm version it pins. Upgrading an install whose vite/node_modules was created with the old store path: delete vite/node_modules once, or pnpm aborts without a terminal with ERR_PNPM_ABORTED_REMOVE_MODULES_DIR_NO_TTY.

  • module-modern-frontend 2.20.0 — HMR off by default; contract validated before writing and regenerated only on module-list writes; CMS delta kept on a failed compile and Page Builder classes skipped; inline styles back on the payment pages and a CSSOM pre-paint; deploy warning for themes with no Vite build; Adobe Commerce storefront inventory; PHP 8.3 and Magento 2.4.7
  • module-modern-frontend-cli 2.8.0 — Adobe Commerce section in the doctor; source-writing commands refuse production mode; requires core ^2.20
  • component-modern-frontend 2.6.0 — drop our environment's pnpm settings from the harness; require engine ^3.1.0 and Node 22.13
  • mage-obsidian 3.1.0 — validate dev server settings only with --dev-server
  • module-catalog 3.12.0 — place the filter column where the page layout declares it
  • theme-base 3.13.1 — give the side columns of 2columns-right and 3columns the classes the filter column needs
  • module-storefront 3.22.0, module-showcase 1.5.0 — ship the collected en_US dictionary
  • PHP 8.3 floor: module-catalog-search 2.2.0, module-checkout 3.12.0, module-customer 2.4.0, module-downloadable 2.2.0, module-gift-message 2.2.0, module-instant-purchase 2.2.0, module-inventory-stock-visualizer 1.2.0, module-modern-frontend-twig 2.7.0, module-multishipping 2.1.0, module-persistent 2.1.0, module-product-alert 2.1.0, module-review 2.3.0, module-sales 2.4.0, module-search 1.3.0, module-send-friend 2.2.0, module-vault 2.3.0, module-wishlist 2.3.0

August 2026

Checkout served from the full-page cache

The checkout is now a cacheable public shell with the private half delivered through customer-data, instead of an uncacheable page. The shell can be toggled per store.

  • module-checkout 3.3.0 — serve the checkout page from the full-page cache; seed the island from the customer-data section; fill the shipping form from the customer address book; show selected options under each summary line
  • module-modern-frontend 2.14.0 — cacheable checkout shell flag
  • module-modern-frontend 2.15.0 — the section store reports whether its cached snapshot is unsynced
  • theme-default 3.8.0 — inline only the cacheable half of the checkout config; label the saved address picker

Cacheable listing fragments

Layered navigation, sorting and paging are served as cacheable fragments, so a filtered listing no longer costs a full uncached page render.

  • module-search 1.0.0 — new module: filters, sorting and paging as cacheable fragments
  • module-storefront 3.7.0 — announce listing navigation so enhancers rebind after a swap

Feature switchboard for demo stores

  • module-showcase 1.0.0 – 1.2.0 — new module: switch MageObsidian features per visitor, offer the cacheable checkout as a visitor switch, and report the active feature set as New Relic attributes

Static deploy verification

Static deploy verification no longer cries wolf. The check added in module-modern-frontend 2.15.0 read --language's default value, all, as if it were a locale, so it looked under a pub/static/<area>/<theme>/all/ that Magento never writes and reported a flawless deploy as entirely missing. It now resolves the sentinel through Magento's own LocaleResolver, honours --theme, --exclude-theme and --exclude-language, and warns instead of aborting the deploy.

  • module-modern-frontend 2.15.1 — resolve --language all through LocaleResolver; warn instead of aborting

July 2026

The month the storefront line moved to 3.x (21 July) and then grew a reactive layer on top of it.

Optimistic UI and a typed storefront event bus

Every cart, wishlist, compare, catalog and checkout mutation now dispatches before / after / failed events on a typed bus. The UI projects the change before the server confirms it and settles when it does — counters flash, toasts fire, and in-flight operations are tracked centrally.

  • js-package-utils 2.5.0 — observer-style event manager
  • js-package-utils 2.6.0 — typed storefront events with sticky dispatch and a DOM mirror; patchSection for projecting a change ahead of the server; in-flight operation tracking; optimistic-UI runtime config
  • module-modern-frontend 2.11.0 — storefront event manager singleton
  • module-modern-frontend 2.12.0 — island lifecycle events and section patching wired into the runtime; optimistic-UI storefront flag
  • module-storefront 3.2.0 – 3.4.0 — events around every cart mutation; cart, wishlist and compare mutation events; search mutation events from the autocomplete; toasts driven by the notification event; the optimistic feedback layer for buttons, notices and value flashes
  • module-checkout 3.1.0 — cart page driven by the event bus; checkout mutation and step-change events; mini-cart items removed optimistically
  • module-catalog 3.1.0, 3.3.0 — variant, bundle, gallery and product-option events

Islands that hydrate over server-rendered markup

Islands no longer pop in over an empty container: the server renders the markup the island adopts, and development builds report hydration drift when the two disagree.

  • module-modern-frontend 2.9.0 — server-side placeholder inside island markers
  • module-modern-frontend 2.11.0 — islands rendered with hydratable server markup; hydration drift reported in development builds; doctor flags eager islands that render an empty container
  • js-package-utils 2.5.0 — mount islands from server markup and diff for drift; island-ssr CLI to render an island's initial markup
  • js-package-utils 2.6.1 — flag a marker once its island has finished rendering
  • module-modern-frontend-twig 2.3.0 — island markup and icon classes exposed to templates
  • theme-default 3.2.0 — server-render the markup hydrating islands adopt

Personalised content drawn before the first paint

Customer-data counters and the sign-in state are painted from a declaration in di.xml, before the first frame, so personalisation no longer arrives as a visible flicker.

  • module-modern-frontend 2.12.1 — draw customer-data counters before the first paint
  • module-storefront 3.4.3 — declare the header counters
  • module-customer 2.0.4 — account flag declared and the sign-in placeholder gated
  • theme-default 3.4.5 — the pre-paint runtime owns the sign-in placeholder

Tailwind for CMS content

Classes typed into CMS pages and blocks were invisible to the build. Content is now exported, scanned and compiled on demand, served as a delta stylesheet behind a stable URL and an ETag.

  • module-modern-frontend 2.11.0 — compile Tailwind classes the build never saw; export content for scanning; delta stylesheet from a stable URL with an ETag; per-page/block opt-out; the Icon component and Vue islands placeable from content via widget and directive
  • module-modern-frontend-cli 2.4.0 — cms:export and cms:jit commands, wired into the doctor
  • js-package-utils 2.5.0 — scan exported CMS content for Tailwind classes and pin the list per theme

Cross-document view transitions

  • module-storefront 3.3.0, 3.4.0 — transitions scoped to catalog moves; product cards reordered with duplicate names guarded
  • module-catalog 3.2.0, 3.3.0 — the gallery image named as the card morph target; cards classed and the gallery swap calmed
  • theme-default 3.3.0, 3.4.0 — the chrome held still across transitions; rules moved into a stylesheet, animating cards and cart lines

A shared field system and UI primitives

  • module-storefront 3.4.0 — a shared field component with required and error states; checkbox and slot primitives; button, link and field primitives as layered components
  • module-storefront 2.1.0 — priority+ primary nav island with an overflow menu
  • module-storefront 2.2.0 — nested mega menu with desktop flyouts and a mobile accordion; configurable mobile brand and home link
  • module-storefront 3.1.0 — cache-tagged nav block for ESI fragments; menu tree cached in block_html with a 1 h TTL; category URL rewrite lookups batched into one query
  • module-catalog 3.5.0 — layered navigation as a drawer on mobile
  • theme-default 3.1.0, 3.4.0, 3.7.0 — nav blocks served as ESI fragments with a TTL; the primary nav split by container queries instead of client-side measuring; drawer filters and a two-row mobile toolbar

One-page checkout layout

The checkout ships in two layouts behind a config flag: the stepped wizard, or a reactive one-page layout.

  • module-checkout 2.1.0 — reactive one-page checkout layout
  • module-modern-frontend 2.8.0 — checkout layout mode config flag
  • module-checkout 2.2.0 — native checkout configuration respected (agreements, guest login, summary cap, display_billing_address_on)

MSI stock visualizer

  • module-inventory-stock-visualizer 1.0.0 — new module: an availability panel routed by product type, redesigned around a segmented source rail, server-rendered and skipped entirely for out-of-stock products

Twig engine

  • module-modern-frontend-twig 2.1.0 – 2.5.0 — placeholder markup forwarded through render_vue; namespace aliases and @parent template inheritance; inline_view_file to embed a view file verbatim; script() to load a Vite enhancer without a rendering block

Diagnostics

  • module-modern-frontend 2.10.0, 2.11.0 — detect a page cache key that ignores X-Magento-Vary; report the Tailwind binary and unresolved CMS classes
  • module-modern-frontend-cli 2.3.0, 2.4.0 — page cache vary handling reported; templates scanned for eager islands without hydration

Speculation rules

  • module-storefront 3.6.0 — configurable speculation rules

June 2026 — the 2.0.0 line

The whole stack was cut together on 22 June: core engine, CLI, Vite harness, JS engine, the optional Twig engine, module-storefront, both themes, and the compatibility modules for catalog, search, checkout, customer, sales, wishlist, reviews, vault, gift message, downloadable, multishipping, persistent, product alert, send-friend and instant purchase.

Vue islands

  • module-modern-frontend 2.0.0 — Vue components rendered as lazy-hydrated islands; @api interfaces, drift detection and hardening
  • js-package-utils 2.0.0 — island hydration runtime
  • module-modern-frontend 2.1.0 — customer-data section hydration deferred to idle, off the critical path
  • module-modern-frontend 2.2.0, 2.2.1 — modulepreload of the eager island dependency graph, emitted inline per marker so body-end islands are covered too

Critical CSS

  • js-package-utils 2.4.0 — Beasties critical-CSS extractor
  • module-modern-frontend 2.4.0 — critical-CSS path and per-theme HTML-minify opt-out
  • module-modern-frontend-cli 2.2.0 — critical-CSS generation command
  • theme-base 2.1.0 — stylesheet deferred per page when critical CSS exists

Optional Twig engine

  • module-modern-frontend-twig 2.0.0 — a .twig engine coexisting with .phtml, with i18n, eager mount and html-safe filters, a responsive image helper, a json_ld helper and DI-registered extensions

SEO, images and i18n

  • module-modern-frontend 2.0.0 — schema.org JSON-LD (Organization, WebSite, BreadcrumbList, Product); CWV-friendly image render helper
  • js-package-utils 2.2.0 — i18n facade for plain ESM enhancers
  • module-modern-frontend-cli 2.0.2 — $t phrases collected from .ts and .js sources
  • theme-base 2.0.1 — translation dictionary preloaded off the island bootstrap chain

Developer workflow

  • module-modern-frontend 2.0.0, 2.3.0 — dev diagnostics core and client-side dev-server guard; Vite dev server lifecycle managed via process group; nginx proxy snippet derived from config; DevWorkflow and ThemeSelector
  • module-modern-frontend-cli 2.0.0, 2.1.0 — doctor reports ignored config files; jsconfig and .gitignore scaffolding for editor types; one-shot --up/--down and a theme picker for frontend:dev
  • js-package-utils 2.3.0 — theme prompt when --dev-server omits --theme