The “Perfect” JS Library Tooling
summary
Concrete checklist: write docs first with install, examples and API; ship TypeScript types included (prefer writing in TS so .d.ts are generated); run lint, typecheck and unit tests together via Jest projects; transpile with Babel and emit both CJS and ESM plus a types build from tsc; use GitHub Actions and semantic-release auto-publishes to npm; add CONTRIBUTING, PR templates, .nvmrc and integration tests by locally publishing the package (the presenter supplies a zero‑config CLI that scaffolds this).
AI-written summary · about
chapters (28)
- 0:00Intro
- 1:55What is the benefit
- 2:42The user is the developer
- 3:12Lets do 10 squats
- 6:36The Perfect JS Library
- 7:22Helpful Docs
- 7:48Writing Docs First
- 8:57Types of Docs
- 13:15Typescript
- 13:56Statistics
- 14:53Type Declaration
- 15:37Writing in Typescript
- 17:54Unit testing
- 22:23CI environments
- 23:31Bug Free
- 24:25Issue Templates
- 25:00Bugs
- 25:34Contributing
- 27:56Transpiling
- 31:08Continuous Delivery
- 32:11Release
- 32:27Package
- 32:39Resources
- 32:54Recap
- 33:40Developer Experience
- 35:28Documentation
- 38:36Devops
- 40:48Conclusion
related talks
32mThe "Perfect" Tooling Library
01h 01mUseful Tools and Utils for JS Development
23mJSDocs: It's like TypeScript but without all that TypeScript
23mPublishing in JavaScript Ecosystem: How to Keep Everyone Happy?
24mPublishing in the JavaScript Ecosystem & Keeping Users Happy
33mTypeScript - JavaScript you are gonna love
31mJavaScript That Scales
39mA modern package registry for JavaScript and TypeScript