Magewire V3 - Update
Technical Progress
I've been working hard to refine the framework, tying up loose ends related to support mechanisms, features, and overall extensibility. My goal is to ensure developers can get the maximum potential out of Magewire. I'm really happy with the progress so far and can't wait to see what others build with it. The new ways to hook into processes—both from a backend and a frontend perspective—offer an enormous upgrade.
I've also started working on Hyvä Theme support, making Magewire compatible thanks to the flexibility that Hyvä provides. I believe Magewire V3 will be widely used in combination with Hyvä, so ensuring compatibility makes complete sense. But it doesn’t stop there—other frameworks and themes can also be integrated with Magewire V3. I’ve already explored a few options, but as I mention in my video, my time for Magewire development is limited, so I have to invest it wisely.
Directive Support
A recent addition to Magewire V3 is support for @
-prefixed directives, similar to Blade directives in Laravel. These will only work within Magewire component templates, but I’m really excited about this feature and what it means for productivity. Check out my YouTube video for more details on how it works!
View Instructions
Inspired by my work on Hyvä Checkout, I’ve been experimenting with a new feature called view instructions. This concept is still in its early stages, but the idea is to allow backend developers to write view instructions in PHP and bind them to the frontend—without needing a single line of JavaScript. While this feature won’t make the first release, I see a lot of potential in it.
Backwards Compatibility
This is progressing well, thanks in large part to the work I’ve done for the Hyvä Theme. That said, many aspects won’t be backwards compatible out of the box at launch. However, with contributions from the community and my own efforts, I’m confident we’ll get there! From a JavaScript perspective, some changes will be necessary. To prepare, I recommend checking out the Livewire upgrade guide, which covers most of what to expect.
Release Timeline
The big question: when will Magewire V3 be released? The honest answer—it’s difficult to say. My wife and I are expecting a child very soon (or have already welcomed one by the time you read this!), which means my available time will be even more limited. Nevertheless, I remain committed to continuing my work on Magewire and making it the dream framework I envisioned from the start.
Being Realistic
There’s also a financial aspect to consider. I’m fortunate to have some sponsors who recognize Magewire’s potential and support me where possible. However, up until now, all my work has been done in my free time. While this has been my own choice, and I continue to work on Magewire with passion, I have to be realistic—this approach isn’t sustainable in the long run.
If you enjoy working with Magewire or want to support its development, please visit my GitHub profile for sponsorship details.
Additionally, I’ve been considering a premium package that could be sold on top of Magewire. The open-source package would include all the essentials, while the premium version would offer extra capabilities. This isn’t my preferred route, but it’s something I’m exploring if the current situation remains unchanged.
Growing the Team
I’ve been handling the majority of Magewire V3’s development myself, but I believe it’s time to expand the team—at least on a voluntary basis. I’m already in discussions with a few enthusiastic individuals, and I hope we can find an arrangement that benefits both parties.
If you’re interested in contributing—whether in areas like Admin support, writing tests, or documentation—I’d love to hear from you! Reach out via LinkedIn, Slack, or Discord. Looking forward to connecting!
A new year calls for new Magewire updates! Over the past few months since MageTitans Groningen, I certainly haven't been idle. Magewire as a framework is ready for release, but there are still some uncertainties in various areas that need to be addressed before it can be considered a serious release candidate. In this blog post, I want to zoom in on some key questions that need answering first.