@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 +13 -3
- package/dist/{baseline-AENFLFQT.js → baseline-45AWVXG4.js} +2 -2
- package/dist/{chunk-OHAVLM6P.js → chunk-BTIIFIOD.js} +1 -1
- package/dist/chunk-WO6EZ6AF.js +3900 -0
- package/dist/cli.js +3 -3
- package/dist/index.d.ts +134 -0
- package/dist/index.js +1 -1
- package/package.json +1 -1
- package/dist/chunk-DLRBJYO6.js +0 -1077
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
|