@koordinates/xstate-tree 2.0.7 → 2.0.9
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +5 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,5 +1,10 @@
|
|
|
1
1
|
# xstate-tree
|
|
2
2
|
|
|
3
|
+
[](https://github.com/koordinates/xstate-tree/blob/master/LICENSE)
|
|
4
|
+
[](https://www.npmjs.com/package/@koordinates/xstate-tree)
|
|
5
|
+
[](https://www.npmjs.com/package/@koordinates/xstate-tree)
|
|
6
|
+
[](https://github.com/koordinates/xstate-tree/actions?query=workflow%3Axstate-tree)
|
|
7
|
+
|
|
3
8
|
xstate-tree was born as an answer to the question "What would a UI framework that uses [Actors](https://en.wikipedia.org/wiki/Actor_model) as the building block look like?". Inspired by Thomas Weber's [Master Thesis](https://links-lang.org/papers/mscs/Master_Thesis_Thomas_Weber_1450761.pdf) on the topic. [XState](https://xstate.js.org/) was chosen to power the actors with [React](https://reactjs.org) powering the UI derived from the actors.
|
|
4
9
|
|
|
5
10
|
xstate-tree was designed to enable modeling large applications as a single tree of xstate machines, with each machine being responsible for smaller and smaller sub sections of the UI. This allows modeling the entire UI structure in state machines, but without having to worry about the complexity of managing the state of the entire application in a single large machine.
|
package/package.json
CHANGED