Is the turf(js) greener on the other side?
summary
A JavaScript spatial library with 150 modules that ships as separate packages and gets tens of thousands of downloads a week, but is maintained by a few volunteers working nights. Key engineering moves: consolidating many repos into a monorepo and publishing with lerna, wrestling with ES6 module compatibility, and shipping a v7 alpha that removed jsts dependency to shrink bundle size. Surprises are governance problems — contributor dropouts, unclear decision rules — more painful than the technical debt.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:29Whos behind it
- 2:39Why I got involved
- 3:34What Ive done
- 4:35What Ive learned
- 5:27Packaging and distributing
- 6:16Unexpected challenges
- 6:40Weve been herd the cats
- 7:00Codebase
- 7:49Communications
- 8:33Governance
- 8:59Current situation
- 9:38Managing turf as a project
- 11:18Uniqueness
- 12:00Limitations
- 12:58WebAssembly
- 13:23Summary
related talks
34mTowards a simpler JavaScript ecosystem
32mWhat's Happening in the JavaScript Ecosystem?
35mBrowser Package Management
23mPublishing in JavaScript Ecosystem: How to Keep Everyone Happy?
25mThe state of the JavaScript Community
47m2017 DevFestMN Eric Brandes
53mArchitecting Robust JavaScript Applications
15mIn JavaScript There’s a Package for Everything… and Often for Nothing