Skip to content

Feature History

This list found below provides an overview of newly introduced features across different versions. Each version listed includes a bullet-point summary of what has been added, ensuring a quick and clear understanding of new capabilities.

Versions not included in this log indicate releases where no new features were introduced.

3.6.0

  • Component-state pagination

Components can use WithPagination to track default or named paginator state and call getPage(), previousPage(), nextPage(), gotoPage(), resetPage(), or setPage(). Magewire 3.6 does not synchronize paginator state to the URL and does not ship paginator views; components remain responsible for querying and rendering their current page. See Pagination.

  • Temporary rate-limit lockouts

Repeated rate-limit rejections can now escalate into an opt-in, origin-scoped lockout. Lockout responses include Retry-After, and the browser suppresses further Magewire updates until the deadline expires. See Rate Limiting.

  • Notifier message coalescing

Repeated active notifications with the same message and type reuse one notification, increment its occurrences, and trigger the new update lifecycle. See Magewire Notifier.

  • Template-fragment compiler fix

Compiler-generated @template fragment scopes now call start() before rendering and pair it with the generated end() call.

3.5.0

  • Magento-backed application container

The new app() helper and ApplicationContainer resolve Magento classes, interface preferences, virtual types, Magewire aliases, and request-time bindings through one compatibility API. See Application Container.

  • Request filter pipeline

Incoming update requests can now be checked once, before any component reconstruction. Rejections carry an HTTP status and a deliberately customer-safe message severity. Request-scoped rate limiting now uses this pipeline. See Request Filters.

3.4.0

  • Lazy loading

Components can defer mounting and rendering until page load or viewport intersection. Lazy behavior can be selected with #[Lazy] or the magewire:component:lazy layout argument, with optional request isolation and custom placeholders. See Lazy Loading.

3.3.1

  • Fixed condition parsing when an array offset resolves to null.
  • Removed deprecated ReflectionMethod::setAccessible() usage.
  • Fixed dependency-injection compilation on the Magento 2.4.6 release line.

3.3.0

  • Expression-aware template directives

Directive arguments can preserve PHP expressions, nested arrays, named arguments, and typed true, false, and null values. This powers updated directives such as @translate, @child, and @escapeUrl.

  • Compiler mechanism and cache command

Template compilation moved from an optional feature to the HandleCompiling mechanism. Compiled views can be cleared with bin/magento magewire:compile:clear, optionally scoped with --area. See Handle Compiling.

  • Pluggable multiple-root handling

The response to multiple root elements is now selected through MultipleRootElementDetectionHandlerInterface. The default handler continues to throw an exception.

  • Removed experimental facades

The experimental facade API was removed. Use Magento dependency injection, Magewire's registries, or the application container introduced in 3.5.

3.2.0

  • Themes split into standalone packages

Theme support no longer ships in-tree. The themes/ directory has been removed from the core magewirephp/magewire repository and every theme moved into its own repository and Composer package for better maintainability:

  • magewirephp/magewire-hyva-theme: Hyvä theme support (was themes/Hyva/).
  • magewirephp/magewire-hyva-checkout: Hyvä Checkout support.
  • magewirephp/magewire-admin: Magento admin support (replaces the themes/Backend/ marker).

Install the package(s) for the themes you use. See Theming.

3.1.0

  • Blade-like Echo Compilers

Adds Blade-style echo syntax to the template compiler. Expressions wrapped in {{ }} are automatically escaped, while {!! !!} renders raw, unescaped output, mirroring the familiar Laravel Blade behaviour and making it easier to output values directly within .phtml templates.

  • Theme-aware Compiled View Paths

The compiled views resource path now includes the area and theme. This keeps compiled output isolated per area and theme, preventing collisions and ensuring the correct compiled template is served for each storefront context.

3.0.0

Magewire V3 is a full rewrite that ports the Laravel Livewire v3 core into Magento 2, replacing the hand-written V1 runtime with a formalised pipeline.

  • Livewire V3 Core

The runtime is now based on the Laravel Livewire v3 core, brought over into Magento 2. This modernises the foundation Magewire is built on and aligns its behaviour and concepts with the wider Livewire ecosystem.

  • Mechanisms & Features Pipeline

The old V1 runtime is replaced by a formalised Mechanisms and Features pipeline, providing a structured, extensible architecture for processing component lifecycles.

  • Template Compiler

Introduces a dedicated template compiler, enabling the @ directives, fragments, and other simplified syntax to be transformed into PHP during template compilation.

  • Snapshot-based State Flow

Component state is now managed through a snapshot-based flow, capturing and restoring component data between requests in a predictable, serialisable manner.

  • Backwards Compatibility Layer

Ships a first-class backwards compatibility layer for V1 components, allowing existing V1 components to keep running on the V3 runtime.

Upgrading from 1.x? See UPGRADING.md.

Note: Requires PHP 8.2 or higher. Support for all PHP versions below 8.2 has been dropped.

3.0.0-beta1

  • Dedicated Documentation

Unlike V1, Magewire V3 now features its own dedicated, GitHub-hosted documentation, powered by MkDocs.

By moving the documentation out of the core repository and into a centralized location, we aim to provide a more structured and accessible knowledge base.

This dedicated space makes it easier to find answers, stay up to date, and get inspired, ultimately helping developers build better, more powerful features with Magewire.

  • Template @ Directives

Using template @ directives allows developers to write simplified syntax that is transformed into more complex PHP code during template compilation. Templates are automatically recompiled whenever a .phtml file is modified, ensuring changes are always up to date.

  • Template Fragments

Provides the ability to mark a specific area within a template, allowing modifiers to alter its content, such as making inline scripts CSP compliant. This is done using the $fragment = $viewModel->utils()->template()->fragment() chain, followed by $script = $fragment->script()->start() and $script->end() to define the fragment boundaries.

For more details, please refer to the Fragments documentation.

  • Automatic View Model Resolving

Blocks that are direct or indirect children of the magewire block will automatically receive a view_model argument, as long as it hasn’t already been manually defined. This reduces the need to explicitly bind the view_model to each individual block, resulting in cleaner and more maintainable layout XML.

For more details, please refer to the Notables documentation.

  • Portman

A tool that enables developers to port packages from other communities into Magento, making it possible to reuse a wide range of existing code and reduce duplication across ecosystems.

For more details, please refer to the Portman documentation.

  • CSP Complaint

Since April 2025, it is recommended that all payment-related functionality is CSP compliant, meaning that any scripts, styles, or other resources involved in the payment process must adhere to Content Security Policy standards.

This includes using nonces or hashes for inline scripts and ensuring that all external resources are loaded from trusted, whitelisted domains. Doing so enhances the security of the checkout process and helps prevent cross-site scripting (XSS) attacks.

  • Components Hooks

Compared to V1, Magewire V3 introduces a wide range of new extension points throughout the backend architecture. Developers can now hook into various stages of the component lifecycle, including rendering, hydration, dehydration, and more, making it easier to customize and extend Magewire's behavior in powerful and flexible ways.

  • View Model Utilities

The primary Magewire ViewModel has been extended with a utils API, giving developers easy access to commonly used tools, both within and outside Magewire component template files. This eliminates the need to repeatedly create custom ViewModels for basic functionality.

The utils API is designed to be extensible, allowing you to add custom utilities when needed. However, in most cases, it should already provide everything you need out of the box.