cut-at-k 0.1.0 → 0.1.1

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.
Files changed (2) hide show
  1. package/README.md +2 -4
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -15,13 +15,11 @@ The second one is where things are usually wrong, and it is quiet when it is wro
15
15
  which is why a loop is better at finding it than reading the code.
16
16
 
17
17
  ```bash
18
- git clone https://github.com/roshcompanylabs/cut-at-k
18
+ npm install cut-at-k
19
19
  ```
20
20
 
21
- Not on npm yet. Zero dependencies, so a clone is the whole install.
22
-
23
21
  ```js
24
- import { severAtEveryPoint, summarise, format } from './src/index.js';
22
+ import { severAtEveryPoint, summarise, format } from 'cut-at-k';
25
23
 
26
24
  const report = await severAtEveryPoint({
27
25
  events, // the whole stream, in order
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "cut-at-k",
3
- "version": "0.1.0",
3
+ "version": "0.1.1",
4
4
  "description": "Cut a stream at every point and check what the consumer is left with",
5
5
  "type": "module",
6
6
  "exports": {