@prairielearn/run 1.0.7 → 1.0.8
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/CHANGELOG.md +6 -0
- package/README.md +2 -2
- package/package.json +2 -2
package/CHANGELOG.md
CHANGED
package/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# `@prairielearn/run`
|
|
2
2
|
|
|
3
|
-
A small utility for emulating expression-oriented programming,
|
|
3
|
+
A small utility for emulating expression-oriented programming, inspired by <https://maxgreenwald.me/blog/do-more-with-run>.
|
|
4
4
|
|
|
5
5
|
## Usage
|
|
6
6
|
|
|
@@ -38,6 +38,6 @@ While the nested ternary is more concise in this example, it's more difficult to
|
|
|
38
38
|
|
|
39
39
|
## Why?
|
|
40
40
|
|
|
41
|
-
Max Greenwald has a great blog post that explains the rationale for this pattern: https://maxgreenwald.me/blog/do-more-with-run
|
|
41
|
+
Max Greenwald has a great blog post that explains the rationale for this pattern: <https://maxgreenwald.me/blog/do-more-with-run>
|
|
42
42
|
|
|
43
43
|
Why is this one-liner a package? Mostly so the documentation and rationale can be kept in one place.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@prairielearn/run",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.8",
|
|
4
4
|
"type": "module",
|
|
5
5
|
"repository": {
|
|
6
6
|
"type": "git",
|
|
@@ -20,7 +20,7 @@
|
|
|
20
20
|
"chai": "^5.2.0",
|
|
21
21
|
"mocha": "^11.1.0",
|
|
22
22
|
"tsx": "^4.19.3",
|
|
23
|
-
"typescript": "^5.8.
|
|
23
|
+
"typescript": "^5.8.3"
|
|
24
24
|
},
|
|
25
25
|
"c8": {
|
|
26
26
|
"reporter": [
|