summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorAsko Nõmm <asko@nmm.ee>2025-04-28 23:54:22 +0300
committerAsko Nõmm <asko@nmm.ee>2025-04-28 23:54:22 +0300
commit4cdeb61f46bed511850f7fc7646bdca27f72132e (patch)
tree1242d37833b750925c6ee544d42fcc8886e4306f /README.md
parentb08c553749f6619815c171175dd6bcf8ee6ab035 (diff)
Allow nothing to be returned by a subscription. Update README.
Diffstat (limited to 'README.md')
-rw-r--r--README.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/README.md b/README.md
index 9ff91b8..0669c12 100644
--- a/README.md
+++ b/README.md
@@ -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/shapex";
+import { ShapeX } from "shapex";
type AppState = {
counter: number;
@@ -51,7 +51,7 @@ npm install 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/shapex";
+import { ShapeX } from "shapex";
type AppState = {
counter: number;