Performing Laparoscopic Lockfile Surgery
summary
A toolchain is built to stop blind lock-file edits: a command-line dependency selector language plus a browser GUI that scans node_modules and lock files, returns JSON via volt query, and shows which workspaces pull which versions. Live demos reveal 2,635 total deps in one project, six different Next versions collapsing to three React versions, and five TypeScript versions — concrete counts that drive action. The tool runs locally, fetches npm metadata, and currently works well enough for guided surgery while still needing bug fixes.
AI-written summary · about
chapters (10)
- 0:00Introduction and background
- 1:10Why lock files matter
- 3:59JavaScript dependency challenges
- 7:28Current lock file limitations
- 9:14Introducing Dependency Selector
- 13:50Programmatic and CLI usage
- 14:32Demoing the GUI tool
- 24:07Real-world dependency examples
- 27:22Debugging TypeScript versions
- 28:46How to use and contribute
related talks
21mIA para videojuegos con JS
44mReusable Insights from Enterprise Deployments
30mLint Your Code Into the Future
23mProtractor: A New Hope
37mMore Effective Approach To Detecting Potential Deadlocks, DEPT(DEPendency Tracker)
48mBetterer: Incremental Improvement
34mKick ass code editing and end to end JavaScript debugging
37mPainless Testing of Event-Driven Architecture