variablelab/theatre
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
theatre/packages/dataverse
History
Aria Minaei 1c69cb7055 Save prism effects in the prism scope, rather than a WeakMap 
... for easier debugging, but there is a perf regression which I
can't yet quantify as the benchmark suit doesn't support comparisons.
2023-01-04 20:49:43 +01:00
..
devEnv Re-do bundling, compat tests, and extension API (#174) 2022-05-25 00:37:18 +02:00
docs Add hotness details to dataverse docs (#138) 2022-04-29 19:04:21 +02:00
src Save prism effects in the prism scope, rather than a WeakMap 2023-01-04 20:49:43 +01:00
.gitignore Initial OSS commit 2021-06-18 13:05:06 +02:00
LICENSE Initial OSS commit 2021-06-18 13:05:06 +02:00
package.json 0.6.0-dev.3 2023-01-04 20:35:56 +01:00
README.md Improve the documentation of dataverse (#116) 2022-04-06 17:28:08 +02:00
tsconfig.json Build: Add a commonjs bundle to dataverse 2021-06-28 16:37:02 +02:00

README.md

@theatre/dataverse

Dataverse is the reactive dataflow library Theatre.js is built on. It is inspired by ideas in functional reactive programming and it is optimised for interactivity and animation. Check out the Get started guide for a more practical introduction.

Dataverse is currently an internal library. It is used within Theatre.js, but its API is not exposed through Theatre. This is so that we can iterate on the reactive internals while keeping the public API stable. We plan to eventually have an LTS release, but for now, expect a high release cadence and API churn in dataverse while the API in Theatre.js remains stable.

Documentation