Manish Kumar

Work03 of 06

Keeping a large Angular app current

Major modules of a production app moved onto current Angular LTS releases, with legacy screens refactored into reusable components along the way.

Company
Cyzerg
Years
2021 to 2024
Role
Frontend developer
Stack
TypeScript, Angular
Where this sits: Junior Angular Developer, CyzergSelectedApr 2021 to Jan 2024
Roles by date
CompanyRoleFromToStack
VenturepactAssociate Software DeveloperJun 2019Apr 2021TypeScript, Angular, Node.js, Express, MongoDB, Redis
CyzergJunior Angular DeveloperApr 2021Jan 2024TypeScript, Angular
CyzergMid-Level Angular DeveloperJan 2024nowTypeScript, Angular, React, Python
LTS 1LTS 2LTS 3LTS 4LTS 5module 1module 2module 3module 4one module per release, never all at once
Figure. a staircase of version steps, each step a module crossing to the next long-term-support release.

Context

An app that falls behind on framework versions collects security warnings, slow builds and code nobody wants to touch. Every skipped release makes the next one harder.

Approach

Upgrade one module at a time on supported LTS releases, and refactor what gets touched into reusable components instead of porting legacy code line for line. Each step stays small enough to review and release on its own.

What shipped

Major modules on current Angular LTS, better security posture and load performance, and a component library the next features were built from.