Reference
Extractor engines
The platform engines a binding can configure, and the first-party bindings that wrap them.
A binding names one platform engine. The engine is platform code; the binding is data. What a route may declare follows from its engine: engines that read a snapshot accept login, load, ready, on and scroll; engines that never open the page reject them.
| Engine | Reads | Document | Emits | Available |
|---|---|---|---|---|
dom@1 | snapshot | required | the transform input | yes |
reader@1 | snapshot | none | app.fruitful.content.webDocument | yes |
media@1 | url | none | app.fruitful.media.video, app.fruitful.media.audio | yes |
rss@1 | body | required | the transform input | declared only |
http@1 | body | required | the transform input | declared only |
First-party bindings
Platform packages are already in every registry and are only ever pinned, never shipped:
app.fruitful.binding.reader(reader@1)app.fruitful.binding.video(media@1)app.fruitful.binding.audio(media@1)