@fusion.dev/helix-diagnostics 0.0.9 → 0.0.10

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 (3) hide show
  1. package/LICENSE +21 -0
  2. package/README.md +37 -0
  3. package/package.json +2 -2
package/LICENSE ADDED
@@ -0,0 +1,21 @@
1
+ MIT License
2
+
3
+ Copyright (c) 2026 Fusion Development Group
4
+
5
+ Permission is hereby granted, free of charge, to any person obtaining a copy
6
+ of this software and associated documentation files (the "Software"), to deal
7
+ in the Software without restriction, including without limitation the rights
8
+ to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
9
+ copies of the Software, and to permit persons to whom the Software is
10
+ furnished to do so, subject to the following conditions:
11
+
12
+ The above copyright notice and this permission notice shall be included in all
13
+ copies or substantial portions of the Software.
14
+
15
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
16
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
17
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
18
+ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
19
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
20
+ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
21
+ SOFTWARE.
package/README.md ADDED
@@ -0,0 +1,37 @@
1
+ # @fusion.dev/helix-diagnostics
2
+
3
+ Finds the Helix mistakes that are valid CSS and therefore silent: a `::part()`
4
+ naming a part nothing publishes, a custom property named for the wrong family, a
5
+ part a composed component never forwarded, two copies of the library on one page.
6
+
7
+ ```sh
8
+ npm install --save-dev @fusion.dev/helix-diagnostics
9
+ ```
10
+
11
+ ```js
12
+ import { diagnose, report } from '@fusion.dev/helix-diagnostics'
13
+ import headless from '@fusion.dev/helix-headless/custom-elements.json' with { type: 'json' }
14
+
15
+ report(diagnose({ tiers: [headless] }))
16
+ ```
17
+
18
+ `diagnose` needs at least one manifest and says so rather than defaulting: with
19
+ none, every part name is unknown and every finding would be noise. `report` is
20
+ the console sink; the `Report` it returns is the same object, so you can send it
21
+ somewhere else instead.
22
+
23
+ None of these produces an error anywhere. They are detectable only against the
24
+ custom elements manifest, which every Helix package already publishes, so the
25
+ diagnostic cannot drift from what is true.
26
+
27
+ **Coverage is half the return value, not a footnote.** A cross-origin stylesheet
28
+ throws on `.cssRules`, so a run that read three sheets of nineteen returns the
29
+ same empty findings array as one that read all nineteen. Read `coverage` before
30
+ you believe `findings`.
31
+
32
+ Development only. It walks stylesheets in the page and makes no network calls,
33
+ ever.
34
+
35
+ [Documentation](https://helix.fusion.dev)
36
+
37
+ MIT
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "@fusion.dev/helix-diagnostics",
3
3
  "description": "Finds the Helix mistakes that are valid CSS: dead parts, misnamed hooks, two copies of the library.",
4
- "version": "0.0.9",
4
+ "version": "0.0.10",
5
5
  "license": "MIT",
6
6
  "author": "Ross Sheppard <ross.sheppard@fusion.dev>",
7
7
  "repository": {
@@ -29,7 +29,7 @@
29
29
  },
30
30
  "bugs": "https://github.com/project-fusion/fusion/issues",
31
31
  "devDependencies": {
32
- "@fusion.dev/helix-testing": "0.0.9",
32
+ "@fusion.dev/helix-testing": "0.0.10",
33
33
  "@types/bun": "^1.3.0"
34
34
  },
35
35
  "homepage": "https://fusion.dev",