Invisible Code: Building JavaScript Libraries For Non-Technical People

on YouTube ↗26m

" summary

Argues for concrete fixes: builds an AMP viewer with Preact and TypeScript deployed on thousands of sites, often under 15 kilobytes, using iframes for style isolation and queued work (FPS-based) to avoid blocking. Uses Sentry for sampled error reporting but implements a tiny shim to push events and an API‑fingerprinting system that dynamically polyfills Fetch (wraps jQuery if present). Finds Prototype.js pre‑2012 breaks map’s third arg and adapts accordingly.

AI-written summary · about

" chapters (13)

1. 0:00Invisible JavaScript libraries
2. 2:25Non-technical users add third-party code
3. 3:10Constraints of embedded JavaScript
4. 5:25Bandwidth and compatibility
5. 7:57Style isolation with iframes
6. 9:49Pitfalls in embedded libraries
7. 13:01Prototype overrides with Sentry
8. 16:40Heavy error reporting wrappers
9. 18:31Dynamic polyfill loading
10. 21:05Performance tips for JavaScript
11. 22:41Developer ergonomics
12. 25:45Exporting to multiple targets
13. 26:09Summary and responsible coding

" related talks

• 21mAsk not what JavaScript can do for youJon Bretman · JSConf EU 2013
• 42mYour library sucks, and why you should use itPeter Higgins · JSConf.eu 2010
• 40mPIMP Your JS Library or Desgning Non-Shit APIs with JavaScriptDan Webb · JSConf US 2011
• 38mJavascript Considered...UsefulJenn Schiffer · JSConf EU 2019
• 06mLightning talk from Andrey SitnikAndrey Sitnik · ReactiveConf 2017
• 22mBuilding JavaScript for JavaScriptersCassidy Williams · DinosaurJS 2019
• 26mJavaScript Tools at Scale Using Type InformationMark Knichel · JSConf EU 2014
• 24mThe missing guide for deciding between 3rd party library and custom code -JSWORLD 2023Glenn Reyes · JSworld Conference 2023