Core TEA implementation complete with HTTP, JSON decoding, and subscriptions.
| Status | Item | Effort |
|---|---|---|
[x] |
Unit tests for core modules (Tea_Cmd, Tea_Json) |
Medium |
[x] |
Tea_Http module for HTTP requests |
Medium |
[x] |
HTTP example (fetch data, loading states, error handling) |
Small |
[x] |
React 19 / ReScript 12 compatibility |
Small |
[x] |
npm publish configuration (package.json fields, files list) |
Small |
[ ] |
GitHub Actions CI (build, test, lint) |
Small |
[ ] |
API documentation (generated from .resi files) |
Medium |
| Status | Item | Effort |
|---|---|---|
[ ] |
Tea_Storage module (localStorage/sessionStorage) |
Small |
[ ] |
Form example with validation |
Medium |
[ ] |
TodoMVC example (proves complete CRUD) |
Medium |
[ ] |
Performance benchmarks |
Small |
After MVP, expand the ecosystem:
-
Tea_Navigation - Client-side routing
-
URL parsing and building
-
History API integration
-
Route-based subscriptions
-
Nested routes
-
-
Tea_Http enhancements
-
Request cancellation
-
Retry policies
-
Caching strategies
-
File uploads
-
-
Tea_Storage
-
localStorage commands
-
sessionStorage commands
-
IndexedDB (maybe)
-
-
Tea_Ports
-
Type-safe JS interop
-
Port-based subscriptions
-
Encoder/decoder helpers
-
Time-travel debugging:
-
Message history
-
State snapshots
-
Replay functionality
-
Export/import sessions
-
Browser DevTools integration
Declarative animations:
-
Spring physics
-
Keyframe animations
-
Subscription-based animation loop
-
Interruptible animations
-
Property-based testing helpers
-
Snapshot testing for views
-
Command/subscription mocking
-
Integration test utilities
See CONTRIBUTING for how to propose changes.
Priority is determined by: 1. User demand (issues, discussions) 2. Ecosystem gaps (what’s blocking real-world use) 3. Maintainer capacity