Check changes in Angular 19 and plan updates

[evilaliv3]

Proposal

This ticket is to track the activities related to checking changes in Angular 19.

It should be verified:

• If the globaleaks codebase should be updated in relation to usage of outdated functions.
• Verify possibilities of optimizations to be adopted on new code
• Verify which are the dependencies that still miss support for Angular 19

List of dependencies that might require to be updated to Angular 19:

• Support Angular 19 ng-bootstrap/ng-bootstrap#4779
• Update to Angular 19 flowjs/ngx-flow#123

[evilaliv3]

@msmannan00 : Do you mind move forward this analysis? thank you if you could.

[msmannan00]

sure, will check it out. angular releases a new version. At the moment there are no code breaking changes just overall improvements in signal concept. Remember flicker issue in images due to zone js that continuously check for changes. Now angular is moving from this to a signal based approach but some things introduced at the moment are experimental but will look at it in detail

[msmannan00]

@evilaliv3 I have updated the code base
https://github.com/globaleaks/globaleaks-whistleblowing-software/tree/dependencies-update

Overall, everything is functioning well, including the test cases, with only minor deprecated features being updated and resolved. Interestingly, this update brings several significant improvements in state management and performance without requiring any code changes. Some highlights include:

1. Enhanced Ivy Rendering Engine: The updated engine improves component rendering efficiency while reducing memory usage.
2. RxJS 8 Integration: Performance optimizations and the introduction of new operators enhance overall efficiency.
3. Improved Change Detection: Optimized mechanisms reduce unnecessary computations, resulting in faster UI updates.
4. Automatic Code Splitting: Smaller bundle sizes and faster loading times are now managed automatically.
5. Deferred Loading: Built-in support for lazy-loading components boosts initial page load performance.
6. Improved Tree-Shaking: Refinements in tree-shaking lead to smaller bundle sizes, contributing to better performance.

However, a few libraries will need to be replaced in the future due to deprecation. Notable examples include:

1. "node-gettext", which has been deprecated for five years.
2. "@types/marked", which has been deprecated for two years.