Skip to main content
Question

Modern UI - Loss of Browser support for Aurelia 1 @autoinject decorator syntax in tc39 - what is the plan?

  • January 29, 2026
  • 3 replies
  • 103 views

Forum|alt.badge.img+5

I have noticed that Acumatica’s implementation of Aurelia 1 relies heavily on the @autoinject decorator for doing dependency injection into the Modern UI code. My understanding from the Aurelia developers is that this @autoinject decorator will not be browser compliant as of tc39 (https://tc39.es/). Individual browsers will have different timelines for dropping pre-tc39 support, but the generic issue here is that at some point this code will no longer be browser-compliant and will not run in future versions of major browsers.

It seems like before a ton of development effort is put into building new customizations and front end screens that rely on Aurelia 1, there should at least be some discussion of whether the future here is to move to Aurelia 2?

3 replies

Dmitrii Naumov
Acumatica Moderator
Forum|alt.badge.img+7
  • Acumatica Moderator
  • March 20, 2026

@rosenjon 

It is indeed the case that @autoinject is going away. However, there is no immediate pressure, since we control when we change our TypeScript/UI Framework versions. 

 

In the long term, migration to a newer version of the UI framework is inevitable. But it is not currently a part of our short-term roadmap.


Forum|alt.badge.img+5
  • Author
  • Semi-Pro III
  • April 30, 2026

@Dmitrii Naumov I think the pressure comes from the eventual loss of support for pre-TC39 decorator syntax eventually, which will bork Aurelia 1 entirely.

There will always be workarounds...i.e. running legacy browsers or enabling legacy decorator support in future browsers.

However, I just question the amount of lock-in to Aurelia 1 you create in the developer community code base by not beginning a path to Aurelia 2. Everyone developing customizations for Aurelia 1 now is in a way creating technical debt that will have to be paid when there is an eventual conversion to Aurelia 2/another frontend framework.


Dmitrii Naumov
Acumatica Moderator
Forum|alt.badge.img+7

running legacy browsers or enabling legacy decorator support in future browsers.

@rosenjon my understanding is that browsers cannot stop supporting pre-TC39 decorator syntax as browsers never actually work with that. It’s transpiled into javascript and only then browser executes it. New Typescript versions can remove that, but the control of the typescript version is completely in our hands here.

 

 

However, I just question the amount of lock-in to Aurelia 1 you create in the developer community code base by not beginning a path to Aurelia 2. Everyone developing customizations for Aurelia 1 now is in a way creating technical debt that will have to be paid when there is an eventual conversion to Aurelia 2/another frontend framework.

 

I don’t think the code most customizations use is very Aurelia specific. It’s mostly declarative anyway.