Back from the past: A tale of helping others upgrade from Angular 1.x

on YouTube ↗20m

" summary

Surveyed teams found time, business incentives and third‑party library gaps block upgrades; a small study called science surfaces time change and typescript as top pain points. Practical fixes include use component‑based 1.5 API to ease migration, migrate CoffeeScript to TypeScript, move to npm/yarn and webpack, and replace Grunt/SEMs; several teams perform incremental rewrites and report reduced risk. Real constraints like IE8 support and staffing limits explain why some projects stay on AngularJS.

AI-written summary · about

" chapters (7)

1. 0:00Intro
2. 0:50Back in time
3. 3:36Modern JavaScript
4. 6:05Trade off
5. 7:58Challenges
6. 9:32Survey results
7. 12:29What can we do

" related talks

• 01h 01mAngular War StoriesDuncan Hunter, Adam Stephensen · NDC Oslo 2017
• 26mUpgrading your AngularJS App, Without the TearsErin Zimmer · NG-MY 2019
• 20mHow to save time & money by planning your ngUpgradeSam Julien · Angular Connect 2018
• 42mHow Angular2 can improve your Angular1 apps todayNir Kaufman · Codemotion Rome 2016
• 11mWhy I'm Excited About Angular for 2018 and 2038Stephen Fluin · ng-europe 2018
• 43mSupporting an Old-Fashioned AngularJS App in a Modern TypeScript WorldJennifer Wadella · RVA JavaScript Conf 2019
• 22mMy Journey on the Angular TeamManu Murthy · AngularConnect 2019
• 23mUpgrading to Angular without ngUpgradeErin Coughlan · Angular Connect 2018