Aurelia

@thekitze We love to see you winning brother. Well deserved.

they bumped my delivery date!!! LFG

rc1 baby 🚀

Read more about what we've just shipped here aurelia.io/blog/2025/12/2…

A few days late, but merry Christmas everyone. We just release beta 27 and it's one of our biggest releases yet. It also lays foundational work for SSR, AOT and SSG support in Aurelia 2. We've also got a new VS Code extension coming and lots more exciting goodies.

Despite the success of other frameworks and libraries, we never wavered or tired. Aurelia is still here. We're not going anywhere 💪

Whoa. We have been cooking these past few weeks. So many good things to come in the next release. Incredible work by the team as always.

@thekitze hello, kitze.

🍿

@mischeiwiller That's actually one of Aurelia’s biggest use cases. We’ve seen numerous companies adopt it for internal webtools where stability and maintainability matter most. Another interesting fact is Aurelia is really popular in Australia. Quite a few companies are using it down there.

TIL that companies use @AureliaEffect for internal webtools

The web already gave us everything we need: HTML, CSS, and JS. A framework should amplify those tools, not replace them with its own dialect. Aurelia treats the platform as the foundation, not a problem to be patched over. That's why Aurelia code feels timeless.

Might be today, might be tomorrow. but we'll have a brand new browser devtools extension out for Aurelia 1 and Aurelia 2 apps. Still a few things to sort out before it's ready, but this is what it's looking like so far. It'll pair nicely with the upcoming Aurelia 2 stable release

We get it. In a world where visibility often wins over substance, staying quiet can make it seem like we’ve disappeared. The truth is we’ve been focused on shipping, supporting long-running production apps, and building Aurelia 2. Our community is small but committed, and the framework is as capable as ever. You’ll be seeing more from us in the coming months, not just code but stories, demos, and resources to show why Aurelia is still a solid choice for building ambitious apps.

@AureliaEffect I’m going to be honest here, I kind of forgot you existed until I saw this tweet. Might be time to hire an evangelist or something…

Not using Aurelia because "nobody else is using it" is the same energy as not sitting at the clean table in high school because it wasn't cool.

Aurelia’s vision remains the same: lightweight, standards based, and easy to integrate anywhere. Many apps built years ago are still running smoothly today. The core team is hard at work on Aurelia 2, and our passionate community continues to grow and support each other. We know Aurelia isn’t the trendiest choice, but trends fade. Our focus has always been stability, performance, and developer happiness. Aurelia 2 will bring modern features while staying true to the principles that have kept apps running reliably for nearly a decade.

@AureliaEffect Aurelia had a clear vision: lightweight, standards-based, integrable with anything, never over-engineered. A rare enterprise opportunity lost to years of delays and lack of critical mass. Momentum is gone, a huge missed chance?

Big frameworks are like big banks. Too bloated to fail. Too confusing to escape. Too late to realize you should’ve just used Aurelia.

@dyowee Technically you could use it now. But official stable release is coming nex! We just had some major binding system stuff to get done which will make everything better. Thanks for your patience 💙

@AureliaEffect When will v2 be out? :)

@_JohnMerchant @waybackmachine Ironically the real problem is the tooling situation. The core libraries themselves are still available via npm. But if you started out with JSPM or Webpack, you're going to have to do some tooling upgrades if you want to modernize.

@AureliaEffect Making a change to the average web app built in 2015 probably now requires at least a few @waybackmachine searches

It’s kind of wild that some of our users have Aurelia 1 apps they built in 2015-2016 still running in production in 2025… No major rewrites. No framework-induced fires. Just quietly doing their job for a decade.

@AureliaEffect Our app was built starting with Aurelia 1 beta in 2015. It's evolved to release versions of version 1 and we still expand the product with ease.

The year is 2025. You're using a JavaScript library (not Aurelia) that bundles a compiler, a scheduler, a streaming engine, and a time-travel debugger. You wanted a form.

The Toyota Corolla doesn't trend. It just gets 500 miles to a tank, starts every single time and runs forever. Aurelia is that. For your frontend.