@plurnk/plurnk-execs-common 1.15.0 → 1.16.0

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/README.md CHANGED
@@ -34,12 +34,12 @@ selects the working directory; the body remains the program
34
34
  ({§executor-subprocess-routing}).
35
35
 
36
36
  ```example
37
- ## EXEC0 (./deploy.sh)
37
+ ### EXEC0 (./deploy.sh)
38
38
  yes
39
39
  yes
40
40
  no
41
41
 
42
- ## EXEC0 [python3] (transform.py)
42
+ ### EXEC0 [python3] (transform.py)
43
43
  3
44
44
  1
45
45
  4
package/docs/node.md CHANGED
@@ -19,7 +19,7 @@ on stderr.
19
19
  Runs in the workspace project root by default, or the daemon's own cwd in a
20
20
  workspace without one; a `{cwd=<directory>}` block on the heading selects
21
21
  another. The target is a script, never a command or a directory:
22
- `## EXEC0 [node] (tool.js)` runs that JavaScript file and receives the body as
22
+ `### EXEC0 [node] (tool.js)` runs that JavaScript file and receives the body as
23
23
  stdin; anything else is refused before anything runs. Relative module and
24
24
  filesystem paths resolve against the working directory. The receipt always
25
25
  names it.
package/docs/sh.md CHANGED
@@ -16,13 +16,13 @@ write — or, in a workspace without one, the directory the shell would run in
16
16
  anyway. A `{cwd=<directory>}` block on the heading overrides it for its body:
17
17
 
18
18
  ```example
19
- ## EXEC0 {cwd=./dir}
19
+ ### EXEC0 {cwd=./dir}
20
20
  pwd
21
21
  ```
22
22
 
23
23
  The receipt always names the directory the command ran in.
24
24
 
25
- A script target runs that script: `## EXEC0 (greet.sh)` runs it with an empty
25
+ A script target runs that script: `### EXEC0 (greet.sh)` runs it with an empty
26
26
  stdin; a nonempty body becomes its stdin. The interpreter reads the script
27
27
  directly, so it needs no executable bit; a script path authored inside a shell
28
28
  body still follows the kernel's ordinary executable-bit rules.
@@ -45,16 +45,16 @@ because either may carry the useful diagnostic.
45
45
  For a long-running command, the `<L>` slot carries `<TIMEOUT_SECONDS, POLL_SECONDS>` (both seconds):
46
46
 
47
47
  ```example
48
- ## EXEC0 <1800>
48
+ ### EXEC0 <1800>
49
49
  npm run build
50
50
 
51
- ## EXEC0 <1800,300>
51
+ ### EXEC0 <1800,300>
52
52
  npm run e2e
53
53
 
54
- ## EXEC0 <-1,300>
54
+ ### EXEC0 <-1,300>
55
55
  npm run test
56
56
 
57
- ## EXEC0 <-1,0>
57
+ ### EXEC0 <-1,0>
58
58
  tail -f app.log
59
59
  ```
60
60
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@plurnk/plurnk-execs-common",
3
- "version": "1.15.0",
3
+ "version": "1.16.0",
4
4
  "description": "Universal subprocess executor for plurnk-service's exec scheme — one package exposing the shell, Node.js, Python 3, and supported host interpreters.",
5
5
  "keywords": [
6
6
  "plurnk",
@@ -250,6 +250,6 @@
250
250
  "prepublishOnly": "npm audit --audit-level=moderate && npm test"
251
251
  },
252
252
  "peerDependencies": {
253
- "@plurnk/plurnk-execs": "^1.15.0"
253
+ "@plurnk/plurnk-execs": "^1.16.0"
254
254
  }
255
255
  }