@fusion.dev/helix-cli 0.186.0 → 0.187.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 +10 -24
  2. package/package.json +6 -6
package/README.md CHANGED
@@ -1,8 +1,8 @@
1
1
  # @fusion.dev/helix-cli
2
2
 
3
- The Helix command line. Holds components to the conventions Helix is built on,
4
- derives themes, scaffolds a project, checks a project's code against the Helix
5
- it installed, and serves the derivation to an agent.
3
+ The Helix command line. Derives themes, scaffolds a project, checks a project's
4
+ code against the Helix it installed, looks up the installed packages, and serves
5
+ all of it to an agent.
6
6
 
7
7
  ```sh
8
8
  npm install --save-dev @fusion.dev/helix-cli
@@ -15,22 +15,22 @@ the package it's missing. To start a project rather than add Helix to one, use
15
15
  `npm create @fusion.dev/helix-app`.
16
16
 
17
17
  ```sh
18
- helix component check # the CI shape: nothing printed on success
19
- helix component audit # every rule and what it found
20
- helix component fix # the rules that can write
18
+ helix scan # your code, judged against the Helix you installed
19
+ helix theme audit # every contrast pair in your theme
20
+ helix mcp init --client claude
21
21
  ```
22
22
 
23
23
  | Verb | What it does |
24
24
  |---|---|
25
- | `component` | Holds components to the conventions. `--only <rule>` runs one of `attributes` `axes` `corners` `events` `hooks` `parts` `reflected` `seeds` `selectors` `ssr` `stable` `tokens` and the rest |
26
25
  | `theme` | `init` a starter intent, `build` it to CSS, `audit` every contrast pair, `check` in CI |
27
26
  | `new` | Scaffolds a project from a Helix template |
28
27
  | `diagnostics` | Receives the runs `initDiagnostics()` sends from your app and prints each new finding. `--out <path>` writes the CI file, `--port` picks the port, 7417 by default, and `--config <path>` names the settings served to the page |
29
- | `scan` | Reads your project's stylesheets, templates, and modules, and prints each finding with its file and line. `--build <dir>` weighs each Helix family in your bundle, `--out <path>` writes the run to the CI file, and `--config <path>` names the settings |
30
- | `mcp` | Serves the derivation to an agent over stdio, as an MCP server |
28
+ | `scan` | Reads your project's stylesheets, templates, and modules, and prints each finding with its file and line. `--build <dir>` weighs each Helix family in your bundle, `--out <path>` writes the run to the CI file, `--config <path>` names the settings, `--file <path>` reports one file's findings, and `--stdin <language>` checks a snippet |
29
+ | `api` | Looks up the installed Helix packages: `find` a family, a `family`'s API, an `example` with its imports, the `imports` for a list of tags, and `tokens` |
30
+ | `mcp` | Serves the same lookups, the scan, and the theme derivation to an agent over stdio, as an MCP server. `mcp init --client claude\|cursor\|vscode` writes the client's configuration |
31
31
 
32
32
  `--json` is on every verb, in a shape a script can read without parsing
33
- sentences: the rules, their counts and their findings. `--no-color` is the third
33
+ sentences. `--no-color` is the third
34
34
  way to turn color off, for a terminal that reports itself capable and is not.
35
35
  Color is already off when stdout is not a terminal and when `NO_COLOR` is set.
36
36
 
@@ -39,20 +39,6 @@ rather than compiled into the binary, so one build serves every release that
39
39
  changes no Rust. A binary built from a checkout of this repository has no such
40
40
  package beside it and says `0.0.0-dev`, which is what that build is.
41
41
 
42
- ## What it reads
43
-
44
- `component` reads the tiers named by a `helix` key in `fusion.json`, or by
45
- `helix.json` where the Fusion CLI is not in use. A rule that needs a
46
- manifest says so rather than reporting a clean tree it never looked at, so a
47
- fresh clone wants `bun run analyze` before the rules that read one mean anything.
48
-
49
- ## Two shapes, one measurement
50
-
51
- `audit` prints every rule and exits 1 on a finding. `check` runs the same
52
- measurement and prints nothing on success. Use `audit` while you work and
53
- `check` in CI, and never both in one script: the difference is what is printed,
54
- never what is judged.
55
-
56
42
  [Documentation](https://fusion.dev/helix)
57
43
 
58
44
  MIT
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@fusion.dev/helix-cli",
3
3
  "description": "The Helix command line, for a workspace that reaches it through npm.",
4
- "version": "0.186.0",
4
+ "version": "0.187.0",
5
5
  "license": "MIT",
6
6
  "author": "Ross Sheppard <ross.sheppard@fusion.dev>",
7
7
  "repository": {
@@ -29,11 +29,11 @@
29
29
  "theme"
30
30
  ],
31
31
  "optionalDependencies": {
32
- "@fusion.dev/helix-cli-darwin-arm64": "0.186.0",
33
- "@fusion.dev/helix-cli-darwin-x64": "0.186.0",
34
- "@fusion.dev/helix-cli-linux-arm64": "0.186.0",
35
- "@fusion.dev/helix-cli-linux-x64": "0.186.0",
36
- "@fusion.dev/helix-cli-win32-x64": "0.186.0"
32
+ "@fusion.dev/helix-cli-darwin-arm64": "0.187.0",
33
+ "@fusion.dev/helix-cli-darwin-x64": "0.187.0",
34
+ "@fusion.dev/helix-cli-linux-arm64": "0.187.0",
35
+ "@fusion.dev/helix-cli-linux-x64": "0.187.0",
36
+ "@fusion.dev/helix-cli-win32-x64": "0.187.0"
37
37
  },
38
38
  "publishConfig": {
39
39
  "access": "restricted"