@rayu-dev/rayu-cli 1.5.11 → 1.5.13

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 (3) hide show
  1. package/README.md +45 -0
  2. package/dist/rayu.js +2017 -1866
  3. package/package.json +1 -1
package/README.md CHANGED
@@ -51,6 +51,51 @@ Or reinstall the latest directly:
51
51
  npm install -g @rayu-dev/rayu-cli
52
52
  ```
53
53
 
54
+ Prefer `rayu update`: it resolves the latest version once, installs that **exact**
55
+ version, and then verifies what actually landed on disk. A plain
56
+ `npm install -g @rayu-dev/rayu-cli@latest` resolves the mutable `latest` tag a
57
+ second time and can silently reinstall the version you already have when npm
58
+ serves cached registry metadata (packuments are cached for 5 minutes), which
59
+ looks like a successful update that changed nothing.
60
+
61
+ When a newer version is published, Rayu shows a one-line notice above the prompt
62
+ and in the welcome box at launch, with a link to
63
+ [the changelog](https://rayucode.com/changelog). Nothing is installed until you
64
+ run `rayu update` yourself.
65
+
66
+ ### Automatic updates (opt-in)
67
+
68
+ Auto-updates are **off by default**. Rayu tells you an update exists but never
69
+ replaces your install behind your back. To turn them on, set `autoUpdates` in
70
+ `~/.rayu/config.json`:
71
+
72
+ ```json
73
+ {
74
+ "autoUpdates": true
75
+ }
76
+ ```
77
+
78
+ To silence update checks and notices entirely:
79
+
80
+ ```bash
81
+ export DISABLE_AUTOUPDATER=1
82
+ ```
83
+
84
+ Two things to know before enabling automatic updates:
85
+
86
+ - **Node version.** Rayu requires **Node.js 18 or newer**. npm only *warns* when
87
+ a package's `engines` requirement isn't met, so if a future release raises that
88
+ floor, an automatic update could replace a working install with one that
89
+ refuses to start until you upgrade Node. `rayu update` has the same
90
+ constraint, but you choose when it happens.
91
+ - **Duplicate installs.** If Rayu is installed under two different npm prefixes
92
+ (for example once with `sudo`, landing in `/usr/local`, and once without,
93
+ landing in `~/.npm-global`), an update writes to whichever prefix npm is
94
+ configured for — which may not be the copy your shell actually runs. The result
95
+ is a "successful" update where `rayu --version` never changes. `rayu update`
96
+ detects this and tells you which copy is shadowing which; the automatic updater
97
+ does not. Run `which -a rayu` to check, and remove the copy you don't want.
98
+
54
99
  ---
55
100
 
56
101
  ## Uninstall