Introduction
The traditional Hyvä reset architecture has been an important part of Magento 2 frontend development for older Hyvä projects. As Hyvä has evolved, the way Magento layout resets are handled has changed significantly. Newer Hyvä Theme versions no longer use the traditional reset-theme parent, introducing a more modern generated base layout reset architecture.
As Hyvä continues to evolve, some important architectural changes have been introduced in recent releases. One of the changes Magento 2 developers should understand is the move away from the traditional Hyvä reset-theme approach.
For businesses planning a modern Magento 2 storefront, Hyvä development can provide a faster and more maintainable frontend architecture.
If you maintain an older Hyvä project, you may be familiar with:
hyva-themes/magento2-reset-theme
and a custom theme that uses:
<parent>Hyva/reset</parent>
However, this is no longer the architecture used by newer Hyvä Theme versions.
Since Hyvä Theme 1.3.18, the Hyvä Theme no longer uses a reset-theme parent.
Hyvä 1.3.21 introduced the Generated Base Layout Reset module, providing a newer approach to handling Magento’s base layout.
This article explains what changed, why Hyvä made this change, what it means for existing Magento 2 projects, and what extension developers should consider when making their modules Hyvä-compatible.
What Was the Hyvä Reset Architecture?
Magento 2 comes with a large amount of frontend functionality designed around the traditional Magento/Luma architecture.
Hyvä takes a fundamentally different approach. It replaces much of the traditional frontend stack with a lightweight architecture based primarily on:
- Alpine.js
- Tailwind CSS
- PHP templates
- Magento layout XML
The official Hyvä documentation describes the theme as a Magento 2 frontend built with Tailwind CSS and Alpine.js instead of technologies such as Knockout, RequireJS, and LESS.
Because many Magento modules add layout XML intended for the traditional frontend, Hyvä needed a mechanism to reset or remove unnecessary blocks and layout instructions.
This was where the reset theme came into play.
Older Hyvä implementations could use:
<parent>Hyva/reset</parent>
The reset theme contained layout reset instructions designed to remove or override Magento frontend elements that were not required by Hyvä.
For developers working on older Hyvä installations, this was an important part of the theme hierarchy.
What Changed in the Hyvä Reset Architecture?
The important thing to understand is that Hyvä did not simply “delete the reset theme.”
Instead, Hyvä changed how base layout resets are handled.
Starting with Hyvä Theme 1.3.18, the Hyvä Theme stopped using a reset-theme parent.
Then, in Hyvä Theme 1.3.21, Hyvä introduced the:
hyva-themes/magento2-base-layout-reset
module.
According to the official Hyvä documentation, the generated base layout reset was introduced to improve TTFB performance for cold-cache requests.
This represents an important architectural improvement.
These architectural changes are also important when evaluating Magento 2 Hyvä-compatible extensions, especially for extensions that add frontend functionality.
Instead of depending on a large collection of static layout reset XML files, Hyvä can generate the required base layout reset information.
Why Did Hyvä Change the Hyvä Reset Theme Architecture?
There are several reasons this approach is useful for modern Magento 2 stores.
1. Improved Cold-Cache Performance
One of the main reasons for introducing generated base layout resets was improving Time to First Byte (TTFB) on cold-cache requests.
Every layout XML file that Magento needs to process can contribute to the amount of work required during page generation.
By generating the relevant reset information, Hyvä can reduce unnecessary layout processing.
This is particularly important for Magento stores where performance is a major business requirement.
2. Less Manual Maintenance
Traditional reset-theme implementations depended on predefined layout XML instructions.
As Magento introduced new modules and changed its frontend structure, reset definitions could require updates.
A generated approach makes it easier for the system to account for the current Magento installation.
This means developers don’t have to think about maintaining a static reset list in the same way as before.
3. Better Compatibility With Magento Changes
Magento continues to evolve.
New Magento modules can introduce additional layout handles and frontend blocks.
A generated reset architecture can dynamically account for the modules present in the Magento installation rather than relying entirely on a fixed set of reset files.
This makes the approach more maintainable as Magento evolves.
What Does the Hyvä Reset Architecture Mean for Hyvä 1.4.0?
Hyvä 1.4.0 represents another major step forward for the Hyvä frontend.
The release modernizes the frontend with Tailwind CSS v4 and Design Tokens, while also introducing improvements such as enhanced HTML structures, BFCache support, Speculation Rules, and View Transitions.
Hyvä 1.4.x uses Tailwind CSS v4, which changes configuration from the traditional JavaScript-based Tailwind configuration toward a CSS-first approach.
Therefore, developers upgrading an older Hyvä project to 1.4.x should not think about the reset-theme change in isolation.
A major Hyvä upgrade can involve several areas:
Hyvä Theme
↓
Theme Module
↓
Base Layout Reset
↓
Tailwind CSS
↓
Design Tokens
↓
Custom Theme
↓
Third-Party Extensions
A proper upgrade should therefore include testing of the complete frontend architecture.
Do Existing Projects Need to Migrate From the Reset Theme?
Not necessarily.
This is an important point for Magento developers.
According to Hyvä’s documentation, migrating an existing custom theme that directly extends Hyva/reset is optional. Existing themes can continue using the reset theme.
So, if you have an older production Magento 2 store running successfully, you should not remove the reset theme blindly.
Instead, first determine:
- Which Hyvä version you are running
- Which reset-theme package version is installed
- Whether your custom theme extends Hyva/reset
- Whether any custom modules depend on the old architecture
- Whether third-party extensions detect Hyvä using the old theme hierarchy
Then plan the migration.
How to Check Your Hyvä Reset Theme Setup
Start by checking your installed Composer packages.
For example:
composer show hyva-themes/magento2-default-theme
You can also check the reset-theme package:
composer show hyva-themes/magento2-reset-theme
If your project contains a custom theme, inspect:
app/design/frontend/Vendor/Theme/theme.xml
Older themes may contain:
<theme xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance”
xsi:noNamespaceSchemaLocation=”urn:magento:framework:Config/etc/theme.xsd”>
<title>Custom Hyvä Theme</title>
<parent>Hyva/reset</parent>
</theme>
This is something worth reviewing during an upgrade.
Migrating From the Legacy Hyvä Reset Architecture
Hyvä provides documentation for migrating custom base themes from the old reset-theme architecture to generated base layout resets.
The migration process depends on how your project is structured.
One important consideration is that Hyvä needs to know which themes should be treated as Hyvä base themes.
For custom base themes, Hyvä documents registering the theme through the Hyva\Theme\Service\HyvaThemes configuration.
This is particularly relevant for agencies and Magento developers who maintain their own reusable Hyvä base themes.
Useful Hyvä Base Layout Reset Commands
Hyvä provides commands that can help developers inspect and migrate base layout reset configurations.
For example:
bin/magento hyva:base-layout-resets:info
The migration tooling can also be used for a custom theme:
bin/magento hyva:base-layout-resets:migrate Vendor/theme
Always review the generated changes before committing them to your production project.
The goal should not simply be to run a migration command and deploy immediately.
Instead:
Backup
↓
Upgrade in development
↓
Run migration
↓
Review generated changes
↓
Test frontend
↓
Test checkout
↓
Test extensions
↓
Deploy
Why the Hyvä Reset Architecture Matters to Magento 2 Extension Developers
This is where the change becomes especially interesting for Magento 2 extension vendors.
Many Magento extensions need to determine whether the current storefront is running Hyvä.
Historically, developers sometimes checked the theme inheritance chain for:
Hyva/reset
For example, custom code may have assumed that a Hyvä theme always inherits from:
Hyva/reset
That assumption is no longer reliable for newer Hyvä implementations.
Hyvä provides theme detection functionality through its theme service architecture. The isHyvaTheme functionality is associated with the newer base layout reset architecture.
This means extension developers should avoid building Hyvä detection logic around a hard-coded assumption such as:
$theme->getParentTheme()->getCode() === ‘Hyva/reset’
Instead, use the supported Hyvä theme detection mechanisms.
This is an important consideration for any Magento 2 extension that provides:
- Hyvä templates
- Hyvä-specific layout XML
- Hyvä JavaScript
- Hyvä CSS
- Hyvä checkout integration
- Hyvä compatibility modules
What Should MageCurious Extension Developers Check?
At MageCurious, we believe Hyvä compatibility should be considered during extension architecture—not added as an afterthought.
When developing or updating a Magento 2 extension for Hyvä, developers should review several areas.
Theme Detection
Don’t assume:
Hyva/reset
will always be present.
Use the supported Hyvä theme detection approach.
Layout XML
Review all layout XML files and identify whether they depend on Luma-specific structures.
Templates
Check whether .phtml templates contain assumptions about:
- Knockout
- RequireJS
- UI Components
- Luma-specific CSS classes
- Magento JavaScript components
JavaScript
Traditional Magento frontend JavaScript may not work correctly in a Hyvä storefront.
Hyvä uses Alpine.js and a different frontend architecture.
CSS
Hyvä’s Tailwind-based architecture requires a different approach to styling.
With Hyvä 1.4.x, developers must also consider Tailwind CSS v4 changes.
Third-Party Integrations
Payment gateways, shipping integrations, product customization tools, tracking modules, and other frontend-heavy extensions should be tested separately.
Hyvä 1.4.0 and Tailwind CSS v4: Another Important Upgrade Consideration
The reset architecture isn’t the only major change developers need to consider.
Hyvä 1.4.0 uses Tailwind CSS v4.
Tailwind v4 changes the configuration model significantly.
Instead of relying primarily on:
tailwind.config.js
Tailwind v4 uses a CSS-first configuration approach.
Hyvä also introduced Design Tokens to make theme customization easier and more consistent.
For existing Hyvä projects, this means a 1.4.x upgrade should include a review of:
tailwind.config.js
CSS imports
Custom utilities
Theme colors
Spacing
Typography
Third-party module CSS
Custom components
Hyvä provides upgrade helper tooling to assist with migrating Tailwind CSS v3 projects to v4.
Hyvä Upgrade Checklist for Magento 2 Developers
Before upgrading an existing Magento 2 store to a newer Hyvä version, we recommend using the following checklist.
Theme
- Check the current Hyvä Theme version
- Check the Hyvä Theme Module version
- Check the current Magento version
- Review custom theme inheritance
- Check whether Hyva/reset is being used
Composer
Review:
composer show hyva-themes/magento2-default-theme
composer show hyva-themes/magento2-theme-module
composer show hyva-themes/magento2-reset-theme
Base Layout Reset
Check:
bin/magento hyva:base-layout-resets:info
If appropriate, evaluate:
bin/magento hyva:base-layout-resets:migrate Vendor/theme
Frontend
Test:
- Homepage
- Category pages
- Product pages
- Search
- Cart
- Customer account
- Login
- Registration
- Checkout
- Forms
- Modals
- Navigation
- Mobile layouts
Extensions
Pay special attention to:
- Payment methods
- Shipping modules
- Product options
- Wishlist
- Reviews
- Search
- Layered navigation
- Analytics
- Cookie/consent modules
- Custom Magento extensions
Hyvä Reset Architecture Frequently Asked Questions
Is the Hyvä Reset Theme completely removed?
Not exactly.
The more accurate description is that newer Hyvä Theme versions no longer use the reset theme as the parent architecture. Hyvä 1.3.21 introduced generated base layout resets, while existing projects can continue using the old reset theme if required.
When did Hyvä stop using the reset-theme parent?
Hyvä’s upgrade documentation states that since release 1.3.18, Hyvä Theme no longer uses a reset-theme parent.
Do I need to migrate my existing Hyvä theme?
Not necessarily.
Migration is optional for existing themes that directly extend Hyva/reset. However, developers should evaluate the benefits of moving to the generated base layout reset architecture when planning a broader Hyvä upgrade.
What is magento2-base-layout-reset?
It is the Hyvä module responsible for the newer generated base layout reset approach. It was introduced with Hyvä Theme 1.3.21 and is designed to improve performance and simplify maintenance of layout reset information.
Does this affect Magento 2 extensions?
Yes, potentially.
Extensions that detect Hyvä by checking for Hyva/reset or rely on the old theme inheritance structure should be reviewed.
Is this related to Tailwind CSS v4?
They are separate changes, but both are important when upgrading to modern Hyvä versions.
Hyvä 1.4.x uses Tailwind CSS v4 and introduces a more modern CSS architecture with Design Tokens.
Final Thoughts
The evolution from the traditional Hyvä reset architecture to generated base layout resets is more than a simple Composer package change.
It represents a broader effort to make Hyvä’s Magento 2 frontend architecture:
- Faster
- Easier to maintain
- More adaptable to Magento changes
- Less dependent on static layout reset definitions
- Better suited for modern Magento development
For existing stores, there is no reason to panic or immediately remove the legacy reset theme or magento2-reset-theme package. The migration should be planned and tested based on the project’s current Hyvä version, theme architecture, and customizations.
For new projects, however, developers should follow the current Hyvä architecture rather than copying patterns from older Hyvä implementations.
The same principle applies to Magento 2 extension developers.
As Hyvä evolves, extensions should avoid relying on assumptions from older versions. Hyvä compatibility should be built around supported APIs, theme detection mechanisms, modern layout architecture, and the current frontend stack.
At MageCurious, we focus on building Magento 2 solutions with modern frontend requirements in mind, including Hyvä compatibility. As a Hyvä Bronze Partner, we continue to follow the evolving Hyvä ecosystem and help Magento merchants and developers build faster, maintainable storefronts.
Working on a Magento 2 store migration to Hyvä or upgrading an existing Hyvä implementation? MageCurious can help you review your theme and extension compatibility and prepare your store for the latest Hyvä architecture.
References
- Hyvä Theme Upgrade Documentation
- Hyvä Generated Base Layout Resets Documentation
- Hyvä 1.3.21 Upgrade Documentation
- Hyvä 1.4.0 Upgrade Documentation
- Hyvä Tailwind CSS v4 Documentation
