weaverbird
weaverbird copied to clipboard
JavaScript backend
For small datasets, transformations could be done client-side. This could be handy to:
- fetch only some data once from a server and dispatch it across usages in the client
- enable offline transformations
- have a standalone version of weaverbird, serverless (not serverless as in "run functions on a server that we don't manage", but as running completely client-side without any server, including for the querying part)