Skip to content

Commit 895ec30

Browse files
committed
feat(blog): add aurelia 2026 roadmap post
Adds a new blog post outlining Aurelia 2's 2026 roadmap and the path to a stable release.
1 parent c1cc491 commit 895ec30

File tree

1 file changed

+90
-0
lines changed

1 file changed

+90
-0
lines changed
Lines changed: 90 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,90 @@
1+
+++
2+
title = "What 2026 Looks Like for Aurelia 2: A Look at the Year Ahead"
3+
authors = ["Dwayne Charrington"]
4+
description = "A stable release is finally happening. Here's what Aurelia 2 looks like in 2026, and what we're doing to ensure Aurelia thrives for years to come."
5+
date = 2026-01-02T10:00:00Z
6+
lastmod = 2026-01-02T10:00:00Z
7+
tags = ["aurelia2", "roadmap", "community"]
8+
+++
9+
10+
Aurelia 2 is getting a stable release in 2026.
11+
12+
We know you have heard variations of this before. We also know Aurelia 2 has been in beta for longer than anyone expected. But 2025 changed things, and we are entering 2026 with more momentum than we have had in years.
13+
14+
## The Long Beta
15+
16+
Let's be direct about it: the beta took too long. A small team, personnel changes, personal challenges some core team members faced, a global pandemic, and structural shifts within the project all contributed to setbacks we did not anticipate. We have admittedly been Duke Nukem Forevering this thing. The difference is we never stopped shipping, and 2025 proved that.
17+
18+
## What We Shipped in 2025
19+
20+
Five beta releases. Hundreds of commits. Here is a sample of what landed:
21+
22+
**Templating and Binding**
23+
- [The `$previous` variable](/blog/2025/12/29/aurelia-beta-27/) in repeaters for comparing items without external state
24+
- [Manual getter dependencies](/blog/2025/12/29/aurelia-beta-27/) with `@computed` for fine-grained performance control
25+
- [Async computed observers](/blog/2025/07/11/aurelia-beta-25/) for predictable, batched change notifications
26+
- Multiple `.class` values in templates
27+
- Value converters now receive binding context for smarter transformations
28+
29+
**Routing**
30+
- [The `loaded` lifecycle hook](/blog/2025/12/29/aurelia-beta-27/), navigation direction detection, and automatic external link handling
31+
- [Aggregated route parameters](/blog/2025/12/29/aurelia-beta-27/) so nested components can access ancestor params
32+
- Path generation for building URLs from named routes
33+
- Navigation strategies for more flexible routing scenarios
34+
- [Clearer package names](/blog/2025/07/11/aurelia-beta-25/): `@aurelia/router-lite` became `@aurelia/router`
35+
36+
**State Management**
37+
- [Multiple named and keyed stores](/blog/2025/12/29/aurelia-beta-27/) for partitioning state into logical domains
38+
- [Middleware support](/blog/2025/07/11/aurelia-beta-25/) for logging, measuring, and transforming actions
39+
- Memoized selectors that cache results until inputs change
40+
41+
**Dialog and UI**
42+
- [Native HTML `<dialog>`](/blog/2025/07/11/aurelia-beta-25/) as the default renderer with CSS animations
43+
- [Child dialog services](/blog/2025/12/29/aurelia-beta-27/) with preconfigured defaults
44+
- [UI virtualization overhaul](/blog/2025/12/29/aurelia-beta-27/) with variable heights, horizontal scrolling, and infinite scroll
45+
46+
**Tooling and Developer Experience**
47+
- [Experimental single file components](/blog/2025/02/05/experimental-single-file-components/) for Vite
48+
- [Storybook support](/blog/2025/02/06/storybook-vite-support/) for both Vite and Webpack
49+
- Vite 6 and Vite 7 support
50+
- Type-checking for non-public members
51+
- CLI improvements: TailwindCSS scaffolding, Storybook integration, default routes
52+
- Toggle `$au` and `$aurelia` on DOM elements for security-conscious apps
53+
54+
**Documentation and Content**
55+
- [Complete documentation overhaul](/blog/2025/08/06/extensive-aurelia-docs-work/) with philosophy docs, better navigation, and improved examples
56+
- New tutorials covering Svelte integration, AI tooling, web workers, websockets, and more
57+
- Video tutorials on AppTasks, synthetic views, and low-level concepts
58+
- A brand new website
59+
60+
And the groundwork for SSR, SSG, and AOT compilation is already in Beta 27. These are not distant roadmap items. They are being actively wired up right now.
61+
62+
## 2026: The Year of Stable
63+
64+
This is the year. Here is what is coming:
65+
66+
- **Stable release**: After years of refinement, Aurelia 2 gets its official stable release
67+
- **Server-side rendering (SSR)**: Vite-based SSR for better SEO and faster initial loads
68+
- **Static site generation (SSG)**: Build static sites with Aurelia 2
69+
- **Ahead-of-time compilation (AOT)**: Smaller bundles and faster startup times
70+
- **VS Code extension**: Typechecking, syntax highlighting, refactorings, and more
71+
72+
We are at the point where we confidently recommend Aurelia 2 for new applications. If you are running Aurelia 1, the [migration roadmap](/blog/2026/1/1/migrating-aurelia-1-to-2-roadmap/) and updated documentation make it easier than ever to start planning your upgrade. Tooling support covers all major bundlers, and the developer experience keeps improving with each release.
73+
74+
## Building for the Long Term
75+
76+
Aurelia is entering its 11th year. The framework has weathered Rob stepping away, team restructuring, and the usual challenges of maintaining open source over the long term. Through all of it, the core mission has not changed: a framework that stays out of your way, respects web standards, and prioritizes developer experience.
77+
78+
Many of you are still running Aurelia 1 apps in production, some for nearly all of those 11 years. That kind of longevity matters to us, and we are working to ensure Aurelia remains sustainable for years to come. This means partnering with organizations that have a vested interest in the framework's success.
79+
80+
We will always remain independent and community-focused. If you look at our Discourse, Discord, and GitHub, you will see we take all feedback, contributions, and ideas into account. That is not changing.
81+
82+
If your company relies on Aurelia and wants to be part of its future, we are open to exploring partnerships. Whether through our [OpenCollective](https://opencollective.com/aurelia), logo placement, sponsored content that fits the Aurelia ethos, or case studies highlighting your work, there are ways to get involved and get your brand in front of the community.
83+
84+
## Start Now
85+
86+
If you have been waiting for the right moment, this is it. The framework is stable in practice, the documentation is comprehensive, and developers have been shipping production applications with Aurelia 2 for years.
87+
88+
Check out the [getting started guide](https://docs.aurelia.io/getting-started/quick-start-guide), join us on [Discord](https://discord.gg/TPV3cvCZhz), and start building.
89+
90+
2026 is going to be a big year for Aurelia. We are glad you are here for it.

0 commit comments

Comments
 (0)