trace-engine-cli 0.0.1 → 0.1.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.
Files changed (2) hide show
  1. package/README.md +14 -32
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -17,47 +17,25 @@ Raw Chromium performance traces are massive (often 20MB–200MB+ uncompressed),
17
17
 
18
18
  ---
19
19
 
20
- ## Installation & Setup
20
+ ## Installation
21
21
 
22
- ```bash
23
- # Clone the repository
24
- git clone https://github.com/ChromeDevTools/trace-engine-cli.git
25
- cd trace-engine-cli
26
-
27
- # Install dependencies
28
- npm install
29
-
30
- # Build TypeScript to dist/
31
- npm run build
22
+ Install [`trace-engine-cli`](https://www.npmjs.com/package/trace-engine-cli) globally from npm to add `trace-cli` to your `$PATH`:
32
23
 
33
- # Link globally across your system
34
- npm link
24
+ ```bash
25
+ npm install -g trace-engine-cli
26
+ trace-cli /path/to/trace.json.gz
35
27
  ```
36
28
 
37
- ---
38
-
39
- ## Using Locally & Pointing AI Agents
40
-
41
- ### 1. Global Command (Recommended)
42
- After running `npm run build && npm link`, `trace-cli` is globally available on your `$PATH`:
29
+ Or run it directly with `npx`:
43
30
 
44
31
  ```bash
45
- trace-cli /path/to/trace.json.gz
32
+ npx trace-engine-cli /path/to/trace.json.gz
46
33
  ```
47
34
 
48
- ### 2. Direct Execution Alternatives
49
- If you prefer not to link globally:
35
+ ---
50
36
 
51
- - **Compiled JavaScript**:
52
- ```bash
53
- node /path/to/trace-engine-cli/dist/bin/trace-cli.js /path/to/trace.json.gz
54
- ```
55
- - **Live TypeScript (no build step)**:
56
- ```bash
57
- npx tsx /path/to/trace-engine-cli/bin/trace-cli.ts /path/to/trace.json.gz
58
- ```
37
+ ## Pointing AI Agents at `trace-cli`
59
38
 
60
- ### 3. Pointing AI Agents at `trace-cli`
61
39
  To equip an AI assistant (or agent in your workspace) to analyze performance traces, add the following instruction to the agent's prompt or project rules:
62
40
 
63
41
  > "To inspect Chromium performance traces (`.json` or `.json.gz`), run `trace-cli <file>`. Inspect the default overview, then use the suggested drill-down commands (`insights`, `tasks`, `find`, `profile`, `diff`, `scheduling`, `network`, `interactions`, `shifts`, `events`, `navigations`) for targeted diagnostics, or `scan <dir-or-glob>` to search across multiple fixtures."
@@ -341,12 +319,16 @@ This compiles a zero-dependency bundle into `src/engine/vendor/trace_engine.js`.
341
319
  ## Development & Testing
342
320
 
343
321
  ```bash
322
+ # Install dependencies, build, and link locally
323
+ npm install
324
+ npm run build
325
+ npm link
326
+
344
327
  # Run test suite (118+ unit tests via node:test)
345
328
  npm test
346
329
 
347
330
  # Run linter and type-checking (Biome & tsc)
348
331
  npm run check
349
- npm run build
350
332
 
351
333
  # Auto-format codebase
352
334
  npm run format
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "trace-engine-cli",
3
- "version": "0.0.1",
3
+ "version": "0.1.0",
4
4
  "description": "CLI tool for inspecting Chromium performance traces on top of DevTools Trace Engine",
5
5
  "type": "module",
6
6
  "bin": {