ripencli 0.1.9 → 0.2.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 +6 -6
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -50,14 +50,14 @@ ripen --help
|
|
|
50
50
|
|
|
51
51
|
## How it works
|
|
52
52
|
|
|
53
|
-
1.
|
|
54
|
-
2.
|
|
55
|
-
3. Shows
|
|
53
|
+
1. Reads your `package.json` and checks each dependency against the npm registry directly — no dependency on any package manager's `outdated` command
|
|
54
|
+
2. Detects your package manager from the lock file (`pnpm-lock.yaml`, `package-lock.json`, or `yarn.lock`) for running updates
|
|
55
|
+
3. Shows outdated packages in a colorful interactive list
|
|
56
56
|
4. Press `v` on any package to pick a specific version from the npm registry
|
|
57
|
-
5. Press `c` to see GitHub release notes between your current and target version
|
|
58
|
-
6. Select the ones you want and press enter — ripen runs the update commands for you
|
|
57
|
+
5. Press `c` to see GitHub release notes between your current and target version
|
|
58
|
+
6. Select the ones you want and press enter — ripen runs the update commands for you, preserving your version range prefixes (`^`, `~`, etc.)
|
|
59
59
|
|
|
60
|
-
When using `ripen -g`, all available package managers are checked in parallel so you see every global package in one place.
|
|
60
|
+
When using `ripen -g`, all available package managers (npm, pnpm, yarn) are checked in parallel so you see every global package in one place.
|
|
61
61
|
|
|
62
62
|
## License
|
|
63
63
|
|