diff options
| author | Asko Nõmm <asko@nmm.ee> | 2025-04-18 18:48:20 +0300 |
|---|---|---|
| committer | Asko Nõmm <asko@nmm.ee> | 2025-04-18 18:48:20 +0300 |
| commit | 3014ce30b733d16cbf79f8e066a30db245e6c59d (patch) | |
| tree | e4a808d58aebbe4c7da31d9ae8a2ffc4b189ce7c /README.md | |
| parent | dd6adf7febf45aa72e9754f13059d40648114027 (diff) | |
Refactor to use Deno for everything.
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 8 |
1 files changed, 3 insertions, 5 deletions
@@ -7,7 +7,7 @@ Create scalable event-driven applications with ShapeX, inspired by [re-frame](ht This is an example application that demonstrates how to use the ShapeX library. It has a single starting point event called `request`, which returns an updated state, which changes the `counter`. When that state changes, the subscriber for the `counter` state fires. ```typescript -import ShapeX from "shapex"; +import ShapeX from "@shapex/shapex"; type AppState = { counter: number; @@ -40,9 +40,7 @@ app.dispatch("request"); ## Installation -```shell -npm i shapex -``` +[ShapeX is available via JSR](https://jsr.io/@shapex/shapex), so check that out for the installation instructions for any given runtime. ## Documentation @@ -51,7 +49,7 @@ npm i shapex At the core of your application is state. You start by initiating ShapeX with some initial state, like so: ```typescript -import ShapeX from "shapex"; +import ShapeX from "@shapex/shapex"; type AppState = { counter: number; |
