Our great sponsors
-
-
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
-
I liked dotProject for internal use, and never exposed installs to the public/web:
https://github.com/dotproject/dotProject
It is certainly legacy... Yet the small footprint works well for standalone ticket resolution databases, task assignment, and budget tracking. Practically speaking, one needs to consider how many staff will be on the interface at a time.
A support database to cover user issue resolutions is part of product development. Having something you know will persist for a decade gets trickier.
I was checking this one. It’s the main branch. https://github.com/kaleidos-ventures/taiga-front/blob/main/p...
Yes.... Just one example if you are curious. At some point NGCC broke parallel builds. https://github.com/angular/angular/issues/38875#issuecomment...
The project I'm upgrading is a library used by other downstream projects. My goal was to release a working version of the library for each Angular release. However, I could never resolve this particular issue and just had to skip that version of Angular.
Another common problem I ran into - dependencies that support, for example, ng11 and ng14 but not ng12 or ng13. So your options are to skip that version of Angular, try to replace or remove the dependency, or beg the author to add support for a version of Angular that is years out of date.
And material components version 15 has a breaking change around custom themes that means either I cannot upgrade to that version, or I have to completely rewrite the entire theming functionality within my project. So yes, I can run ng update @angular/material@15 and migrate the code easily, but that doesn't mean "it just works".
To be clear, I'm not complaining about Angular, or anything else in particular here. In my case, the decisions of the original authors caused upgrading to be more difficult than it needed to be. My point is, without knowing the details of any particular project, it's easy to see how upgrading across several major versions can quickly turn into a nightmare of rewrites.
Related posts
- [AskJS] which framework for frontend and backend to avoid abandoned libraries,breaking changes,terrible debugging features?
- IssueManager - A realtime kanban board made with Appwrite and Angular14
- Angular Signals, Reactive Context, and Dynamic Dependency Tracking
- Episode 24/15: Wiz behind the curtain, Copilot in VSCode
- Always unsubscribe. No exceptions. Debate closed.