visigraph 0.0.3 → 0.0.6

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
@@ -3,7 +3,9 @@
3
3
  Command line for [VisiGraph](https://github.com/textologylabs/visigraph):
4
4
  architecture models you can play through.
5
5
 
6
- Early, pre-1.0. Today it validates a model; the journey player follows.
6
+ Early, pre-1.0. Today it validates a model. Next it builds a static,
7
+ playable site from one: no server, works as a file, a GitLab Pages site or
8
+ a Confluence embed.
7
9
 
8
10
  ```sh
9
11
  npm install -g visigraph
@@ -18,3 +20,29 @@ reference, with a path to each one:
18
20
  ```
19
21
  error: model.yaml:journeys[0].steps[2].endpoint: container 'auth-service' has no endpoint 'token'
20
22
  ```
23
+
24
+ ## Self-update
25
+
26
+ On an interactive launch the CLI checks the npm registry for a newer
27
+ version and offers to update. Saying yes installs the new version and
28
+ re-runs the command you typed on it. Nothing is ever installed without
29
+ that answer.
30
+
31
+ - Skipped entirely in CI, pipes and non-terminal shells.
32
+ - The network check uses the registry npm is configured with (so a
33
+ corporate mirror works), is cached for 24 hours, and gives up silently
34
+ after two seconds. A failed check never blocks or errors the command.
35
+ - Under `npx`, it only prints the newer version and suggests
36
+ `npx visigraph@latest`.
37
+ - `--version` and `--help` never check.
38
+
39
+ Disable it:
40
+
41
+ - per shell or container image: `VISIGRAPH_NO_UPDATE_CHECK=1`
42
+ - centrally, for locked-down or air-gapped environments, in
43
+ `~/.visigraph/config.yaml`:
44
+
45
+ ```yaml
46
+ update:
47
+ check: false
48
+ ```