Justifing Aurelia to myself

I’m at a standstill with my 1.0 to 2.0 conversion. The jump from .25 to .27 has some issue that I don’t understand. Staying on .25 is not an option of course. I work in a world where I can’t openly share code. Sadly, the last 2 days have me trying to justify Aurelia again to myself. I’ve been considering a move to Blazor for quite some time. It is obviously a MAJOR change, one that I may not even be able to complete as I’d have to juggle maintaining legacy while trying to port.

The Aurelia community has been great, core members are always willing to help. I hate to abandon all the work I put in. I like the direction of 2.0, but one thing that always drove me crazy with javascript frameworks is how everything comes together. The simplicity of Blazor in the build department would be fresh air.

I simply don’t have the time to debug the framework and x libraries. I won’t rule out my own bugs as I’m sure I’m doing something wrong somewhere that could be causing my current issues. When all 3 applications in my workspace are dead after going to .27 and fixing the breaking changes, frustration is all I can feel. I already have countless hours in my migration, and the hardest part is yet to come.

A major decision point is ahead of me.

Did you try a code sensitive AI like Codex?

No (used all my premium requests), but I did get through it eventually after a lot of time lost. PNPM workspace package issue. A change to something from .25 to .27 required the application package.json to have some of the aurelia packages for vite to be able to bundle correctly.

"@aurelia/metadata": "catalog:",
"@aurelia/runtime-html": "catalog:",
"@aurelia/kernel": "catalog:"

The build would always succeed, it was a runtime error

My statement above still stands though. I need to make a decision on the future of my project that will probably out live my time on it.

If I stick with Aurelia, I plan to have a skeleton setup for workspaces to share.

1 Like