Confessions of an Ember Addon Author
summary
Claims four concrete criteria for a good Ember addon: it solves an interesting problem, has straightforward setup and docs, exposes a deliberate API and ships meaningful tests; notes the ecosystem has 3,500 add-ons and many fail on docs or tests; demos actual tools and hacks: ember-cli hooks, ember test selectors that strips data-test selectors and removes itself from production builds, ember composable helpers that filters included helpers, ember-cli-deploy adding custom ember-cli commands to automate deploys.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:11Confessions of an Ember Addon Author
- 4:06Documentation Driven Development
- 6:02Any successful project requires two things
- 6:17People are convinced your solution is the best for their problem
- 11:28Addon hooks are powerful
- 12:261. setup Preprocessor Registry II. treeForAddon
- 12:56TREE FOR ADDON Remove addon from build
- 13:34TREE FOR ADDON Remove unused helpers from build
- 15:02WRITING GOOD DOCUMENTATION Tell a story
- 15:33WRITING GOOD DOCUMENTATION What is the public API?
- 16:23WRITING GOOD DOCUMENTATION Show, don't tell
- 17:40Ensure Compatibility With Ember-Try
- 18:38Test With A Real Browser
- 31:381. Addon Anatomy II. One Weird Trick III. Open Sourcery








