tutuca 0.9.82 → 0.9.84

package/README.md

@@ -7,7 +7,7 @@ Zero-dependency batteries included SPA framework.
 - **Fits in your head** (and the context window)
 - **View source friendly** — step through the whole stack
 - **As much HTML as possible, as little JS as needed**
-- ~169KB minified, ~37KB brotli compressed
+- ~177KB minified, ~40KB brotli compressed
 
 ## Quick Start
 
@@ -68,6 +68,8 @@ Tutuca ships a single-file CLI (`dist/tutuca-cli.js`) for inspecting, linting,
 documenting, and rendering components defined in an ES module. The module just
 needs to export `getComponents()` and, for render-time commands, `getExamples()`
 in the storybook shape `{ title, description?, items: [{ title, description?, value, view? }] }` (a single section, or an array of sections).
+Expose **all** of your app's components through `getComponents()` — components
+left out are invisible to `lint`/`render`/`test` and silently lose coverage.
 
 ### Setup
 
@@ -87,8 +89,8 @@ tutuca help [command]
 | Command | What it does |
 |---|---|
 | `get <module>` | Export inventory and counts for the module |
-| `list <module>` | List components and their fields/views |
-| `examples <module>` | List the examples defined in the module's section |
+| `list <module> [name] [--limit n]` | List components and their fields/views (`--limit n` caps, `0` = all) |
+| `examples <module> [--limit n]` | List the examples defined in the module's section (`--limit n` caps, `0` = all) |
 | `show <module> [name]` | Component API docs — all, or one by name |
 | `lint <module> [name]` | Run lint checks — all, or one by name (exit 2 on errors) |
 | `render <module> [name] [--title t] [--view v]` | Render examples to HTML |