The "Perfect" Tooling Library
summary
Claims concrete: write docs before implementation, generate Typescript definitions auto-generated by compiling source, test with Jest plus linting and type checks (run together via Jest projects), run CI on Node 10/12/13 using GitHub Actions, build both ESM and CJS outputs with Babel + TSC, publish automatically with semantic-release, verify package files with unpkg/npm explorer, and use an integrate command that packs a tarball and installs it into a real app to prove exports and deps.
AI-written summary · about
chapters (30)
- 0:00Intro
- 1:12Whats the benefit of all this
- 2:04Whats in this talk
- 2:45Squats
- 3:52Introduction
- 5:41Building the perfect Javascript library
- 6:08Helpful Docs
- 6:33Writing Docs Before Implementation
- 7:39Types of Docs
- 8:56Summary of Docs
- 9:40Typescript
- 10:12Typescript popularity
- 11:03Typescript definitions
- 11:44Why typescript
- 12:57The problem
- 14:06The solution
- 15:01Jeffs Projects
- 17:54Resources
- 19:03Issue Templates
- 19:33Bugs
- 20:09Communication Files
- 21:30Target Formats
- 23:33Continuous Delivery
- 24:32Explorer Tab
- 24:49All Resources
- 24:59Recap
- 25:44Everything on one slide
- 26:43MVP CLI
- 30:16DivOps
- 30:40Wrapup
related talks
46mThe “Perfect” JS Library Tooling
32mTooling Like It's 2025
01h 01mUseful Tools and Utils for JS Development
23mPublishing in JavaScript Ecosystem: How to Keep Everyone Happy?
24mThe Complete Guide to packaging Libraries
24mPublishing in the JavaScript Ecosystem & Keeping Users Happy
18mJavaScript tooling has a blind spot: codebase-wide questions
21mType dependence