Refactoring large JavaScript codebases

on YouTube ↗30m

" summary

Upgrading to newer Node versions and language features forces concrete fixes not vague guidance: promise rejections start terminating processes on Node 16, optional chaining breaks on Node 12, and heavy use of lodash.get inflates CPU cost in huge repos. Two practical routes appear: coordinate owners + lint rules + husky to incrementally ban patterns, or run JS code shift codemods that parse ASTs and rewrite code (author reports tackling 50 000 files quickly). Tests and QA are mandatory; some fixes need human error-handling work.

AI-written summary · about

" chapters (4)

1. 0:00Start
2. 14:28Parsing
3. 16:30Transforming
4. 21:05TTypescript Example

" related talks

• 40mRefactoring large JavaScript codebasesMichele Riva · jsday 2022
• 58mImproving Quality of JavaScript CodeVenkat Subramaniam · JS Fest 2019 Autumn
• 58mImproving the Quality of JavaScript CodeVenkat Subramaniam · Great International Developer Summit 2023
• 20mThey see me refactorin'. They hatin'Vit Gottwald · ReactiveConf 2018
• 34mMass Frontend Refactors: Less Stress; More SuccessWaller Goble · Connect.Tech 2021
• 47mComputer, refactor my code!Zbyszek Tenerowicz · GrillJS 2019
• 43mMachine Powered Refactoring: Leverage AST's to Push Your Legacy Code (& the Web) ForwardAmal Hussein · Node+JS Interactive 2018
• 23mUntangling Your Dependencies: A Pattern for a Well-Knit JavaScript ProjectCarmen Huidobro · Wey Wey Web 2024