reffects - npm Package Compare versions

Comparing version 0.1.18 to 0.1.19

docs/terminology.md

@@ -9,5 +9,5 @@ ## Terminology
 
-If the side-effects and side-causes are just data, how do we do the *actual* work? When you request a `coeffect` or trigger `effect`, `reffects` will look for its handler to do the actual side-effect/side-cause under the hood. For this to work, you'll need to [register your effect handlers](/docs/api.md#registereffecthandler) and your [coeffect handlers](/docs/api.md#registercoeffecthandler) as described.
+If the side-effects and side-causes are just data, how do we do the *actual* work? When you request a `coeffect` or trigger `effect`, `reffects` will look for its handler to do the actual side-effect/side-cause under the hood. For this to work, you'll need to [register your effect handlers](/packages/reffects/docs/api.md#registereffecthandler) and your [coeffect handlers](/packages/reffects/docs/api.md#registercoeffecthandler) as described.
 
-For an `event` to do something, you'll also need to [register its handler](/docs/api.md#registereventhandler). **Here is where your business logic should live.**
+For an `event` to do something, you'll also need to [register its handler](/packages/reffects/docs/api.md#registereventhandler). **Here is where your business logic should live.**
 
@@ -14,0 +14,0 @@ To give you an idea of everything together, this should be a normal flow with reffects:

package.json

 {
   "name": "reffects",
-  "version": "0.1.18",
+  "version": "0.1.19",
   "description": "",
@@ -30,3 +30,4 @@ "source": "src/index.js",
     ]
-  }
+  },
+  "gitHead": "fb8e6654806ae4dabffcbc01259f5bd989424ad9"
 }

No alert changes

Improved metrics

Total package byte prevSize

70099

increased by0.16%

No dependency changes