@vibgrate/cli 0.1.2 → 0.1.4

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
@@ -36,9 +36,19 @@ npm install -D @vibgrate/cli
36
36
  Then scan your project:
37
37
 
38
38
  ```bash
39
- vibgrate scan .
39
+ npx vibgrate scan .
40
40
  ```
41
41
 
42
+ > **Why `npx`?** Installing with `-D` places the binary in `node_modules/.bin/`, which isn't on your system PATH. Use `npx` to run it, or add a script to your `package.json`:
43
+ >
44
+ > ```json
45
+ > "scripts": {
46
+ > "drift": "vibgrate scan ."
47
+ > }
48
+ > ```
49
+ >
50
+ > Then run `npm run drift`. Alternatively, install globally with `npm install -g @vibgrate/cli` to use `vibgrate` directly.
51
+
42
52
  That's it. You'll see a full drift report in seconds.
43
53
 
44
54
  ---
@@ -110,8 +120,8 @@ Beyond the core drift score, Vibgrate runs a suite of extended scanners — all
110
120
  Take a baseline snapshot, then measure drift over time:
111
121
 
112
122
  ```bash
113
- vibgrate baseline .
114
- vibgrate scan . --baseline .vibgrate/baseline.json
123
+ npx vibgrate baseline .
124
+ npx vibgrate scan . --baseline .vibgrate/baseline.json
115
125
  ```
116
126
 
117
127
  ### Multiple Output Formats
@@ -1,8 +1,8 @@
1
1
  import {
2
2
  baselineCommand,
3
3
  runBaseline
4
- } from "./chunk-OHAVLM6P.js";
5
- import "./chunk-DLRBJYO6.js";
4
+ } from "./chunk-BTIIFIOD.js";
5
+ import "./chunk-WO6EZ6AF.js";
6
6
  export {
7
7
  baselineCommand,
8
8
  runBaseline
@@ -1,7 +1,7 @@
1
1
  import {
2
2
  runScan,
3
3
  writeJsonFile
4
- } from "./chunk-DLRBJYO6.js";
4
+ } from "./chunk-WO6EZ6AF.js";
5
5
 
6
6
  // src/commands/baseline.ts
7
7
  import * as path from "path";