@widgetic/dev-tools 0.2.0 → 0.3.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.
@@ -0,0 +1,99 @@
1
+ /**
2
+ * Types for the README contract (`readme-contract.mjs`). Hand-written,
3
+ * dependency-free — same rules as `check-links.d.mts` beside it.
4
+ */
5
+
6
+ /**
7
+ * The canonical sibling-source prose, sentence by sentence. An adopter must
8
+ * carry every sentence verbatim, in order; see {@link readmeFindings}.
9
+ */
10
+ export const CANONICAL_SENTENCES: string[];
11
+
12
+ /**
13
+ * The canonical publish-preparation prose, for the packages in
14
+ * {@link PUBLISH_PACKAGES}. Same matching rules as the sibling sentences.
15
+ */
16
+ export const CANONICAL_PUBLISH_SENTENCES: string[];
17
+
18
+ /** The packages whose READMEs must carry the canonical section. */
19
+ export const ADOPTER_PACKAGES: string[];
20
+
21
+ /** The packages whose READMEs must also carry the publish section. */
22
+ export const PUBLISH_PACKAGES: string[];
23
+
24
+ /**
25
+ * The packages that consume a sibling through a hand-made link to its built
26
+ * output instead of the dev-alias workflow. They are exempt from the canonical
27
+ * sibling-source sentences (they compile no sibling source) but their prose is
28
+ * still scanned for retired link-era instructions.
29
+ */
30
+ export const LINKING_PACKAGES: string[];
31
+
32
+ /** Every package the check reads, in tier order. */
33
+ export const CHECKED_PACKAGES: string[];
34
+
35
+ /**
36
+ * One problem the README contract found in a Frontend checkout. Same fields
37
+ * as the link-doctor's problems, so reporters can treat the two checks alike.
38
+ */
39
+ export interface ReadmeFinding {
40
+ /**
41
+ * - `ldt section missing` — the README has no canonical sibling-source
42
+ * section at all (or no README).
43
+ * - `ldt section drift` — a section exists but its wording diverges from
44
+ * the canonical sentences, or link-era instructions are present. A
45
+ * linking package's README reports only the second kind.
46
+ * - `publish section missing` — a publishing package's README has no
47
+ * canonical publish-preparation section.
48
+ * - `publish section drift` — the section exists but its wording diverges
49
+ * from {@link CANONICAL_PUBLISH_SENTENCES}.
50
+ */
51
+ kind: 'ldt section missing' | 'ldt section drift' | 'publish section missing' | 'publish section drift';
52
+ /** The package directory under `Frontend/` that owns the finding. */
53
+ pkg: string;
54
+ /** What is wrong, README-relative. */
55
+ detail: string;
56
+ /** The action that repairs it. */
57
+ fix: string;
58
+ }
59
+
60
+ /**
61
+ * The stale link-era instructions present in one README's prose (fenced code
62
+ * blocks excluded), as readable labels. Word-bounded, so `pnpm link` does not
63
+ * match the `npm link` pattern.
64
+ */
65
+ export declare function staleInstructionHits(text: string): string[];
66
+
67
+ /**
68
+ * Find what one package's README violates, by tier: an adopter must carry the
69
+ * canonical sibling-source sentences (and a publisher the publish ones), while
70
+ * a linking package must only keep the retired instructions out of its prose.
71
+ * For an adopter an empty `raw` (absent file) yields `ldt section missing`.
72
+ */
73
+ export declare function readmeFindings(
74
+ pkg: string,
75
+ readmePath: string,
76
+ raw: string
77
+ ): ReadmeFinding[];
78
+
79
+ /** Options for {@link collectReadmeDrift}. */
80
+ export interface CollectReadmeDriftOptions {
81
+ /**
82
+ * Package directories to check; defaults to {@link CHECKED_PACKAGES}. The
83
+ * fixture suite overrides this to prove the list is honored. Replaces the
84
+ * former `adopters` option, which set a value on throws rather than
85
+ * silently checking the defaults instead.
86
+ */
87
+ packages?: string[];
88
+ }
89
+
90
+ /**
91
+ * Collect every README finding under a Frontend checkout: each adopter's
92
+ * README must carry the canonical sibling-source sentences, in order, and no
93
+ * README — adopter or linking package — may teach the retired link-era
94
+ * instructions in prose.
95
+ */
96
+ export declare function collectReadmeDrift(
97
+ frontendRoot: string,
98
+ options?: CollectReadmeDriftOptions
99
+ ): { packages: string[]; findings: ReadmeFinding[] };
@@ -0,0 +1,307 @@
1
+ /**
2
+ * The README contract, as data: what each Frontend package's README must say
3
+ * about its sibling-package setup, and how `readmeFindings` reports the ways
4
+ * the prose rots.
5
+ *
6
+ * Two tiers, because two kinds of package consume siblings:
7
+ *
8
+ * - **Adopters** ({@link ADOPTER_PACKAGES}) compile sibling `@widgetic/*`
9
+ * **source** in dev through the dev-alias setup dev-tools owns, and must
10
+ * carry the canonical sibling-source sentences verbatim. The publish tier
11
+ * ({@link PUBLISH_PACKAGES}) adds the publish-preparation sentences.
12
+ * - **Linking packages** ({@link LINKING_PACKAGES}) consume a sibling through
13
+ * a hand-made link to its built output instead — `lps`, `npm link`, a raw
14
+ * `ln -s`. They do not compile sibling source, so the canonical sentences
15
+ * would be false in their READMEs and are not required of them. What does
16
+ * apply is the retired-instruction ban: their prose, like an adopter's,
17
+ * must not re-teach the hand-linking the dev-alias workflow replaced. This
18
+ * tier exists because those three READMEs were read by nothing at all —
19
+ * neither the adopters' check nor any test — so a `npm link` instruction
20
+ * copied back into one would have failed nothing.
21
+ *
22
+ * The section earned its guard by drifting three different ways. It taught a
23
+ * hand-linking practice after the practice was retired (site's `lps` and
24
+ * `pnpm link` lore pointed at a `typescript-sdk` package that no longer
25
+ * existed); it never existed at all in an app that loads dev-tools's alias
26
+ * modules on every dev boot (`file-browser`); and the wording forked per app
27
+ * until a change to the workflow had no single place to land. A contract
28
+ * every README copies by hand is a contract six checkouts hold differently.
29
+ *
30
+ * Everything here is injectable-root pure: `collectReadmeDrift(frontendRoot)`
31
+ * takes the `Frontend/` checkout root and returns the findings found under
32
+ * it, which is what lets the fixture suite build a throwaway checkout, drift
33
+ * it on purpose, and assert on the result without touching real READMEs.
34
+ *
35
+ * Zero dependencies, plain ESM, shipped in the tarball so a consumer can run
36
+ * the check against its own checkout with the installed copy.
37
+ */
38
+
39
+ import { existsSync, readFileSync } from 'node:fs';
40
+
41
+ /**
42
+ * The canonical prose, sentence by sentence. An adopter's sibling-source
43
+ * section must carry every sentence, verbatim, in this order. Matching is
44
+ * ordered-substring over whitespace-collapsed text, so each README wraps the
45
+ * prose to its own line width and may interleave sentences of its own — but
46
+ * any rewrite of the wording fails, because the rewrites are how stale
47
+ * instructions crept back. The last sentence carries the dev-tools link, so
48
+ * a section that stops linking the workflow fails the same way one that
49
+ * misstates it does.
50
+ */
51
+ export const CANONICAL_SENTENCES = [
52
+ 'This app compiles sibling `@widgetic/*` source in dev through the dev-alias setup `@widgetic/dev-tools` owns.',
53
+ 'The alias tables, the `$lib` remap, and everything else the mapping needs come from the installed `@widgetic/dev-tools` dependency.',
54
+ 'An ordinary `npm install` is the whole setup — there is no linking step.',
55
+ 'The why and the silent-degrade failure mode live in [the dev-tools README](../dev-tools/README.md).'
56
+ ];
57
+
58
+ /** The packages whose READMEs must carry the canonical section. */
59
+ export const ADOPTER_PACKAGES = [
60
+ 'chat',
61
+ 'editor',
62
+ 'file-browser',
63
+ 'site',
64
+ 'widget-creator',
65
+ '__template__'
66
+ ];
67
+
68
+ /**
69
+ * The canonical publish-preparation prose, for the packages that publish to
70
+ * the registry. Same matching rules as the sibling sentences: ordered
71
+ * substrings over collapsed prose, app-specific sentences allowed around
72
+ * them. The last two sentences are the discipline the lockfile incidents
73
+ * taught — a consumer whose lockfile never resolved the release was the
74
+ * failure that bit `design-system` and `file-browser` themselves.
75
+ */
76
+ export const CANONICAL_PUBLISH_SENTENCES = [
77
+ 'Publishing starts here: `npm run package` builds the `dist/` directory that is the only content the published tarball ships.',
78
+ 'Linked consumers keep resolving this checkout\u2019s files until the release lands, so a change is not real for anyone else until it publishes.',
79
+ 'After publishing, each consumer package bumps its dependency to the new version and refreshes its lockfile with `npm install`, so `npm ci` resolves the release from the registry.',
80
+ 'A consumer that skips the lockfile refresh keeps resolving the old version, so the version bump and the lockfile refresh land as one commit.'
81
+ ];
82
+
83
+ /** The packages whose READMEs must carry the publish-preparation section. */
84
+ export const PUBLISH_PACKAGES = ['chat', 'file-browser'];
85
+
86
+ /**
87
+ * The packages that consume a sibling checkout through a hand-made link to its
88
+ * built output rather than the dev-alias workflow — `embed-sdk` and `ui-sdk`
89
+ * symlink `@widgetic/api-sdk`, `recorder` links it from its `lps` script.
90
+ * They are exempt from the canonical sibling-source sentences (they compile no
91
+ * sibling source) but not from the retired-instruction ban.
92
+ */
93
+ export const LINKING_PACKAGES = ['embed-sdk', 'recorder', 'ui-sdk'];
94
+
95
+ /** Every package the check reads, in tier order. */
96
+ export const CHECKED_PACKAGES = [...ADOPTER_PACKAGES, ...LINKING_PACKAGES];
97
+
98
+ /**
99
+ * Instructions from the link era that must never come back, word-bounded on
100
+ * both sides. `npm link` cannot match inside `pnpm link` (the boundary fails
101
+ * before the `npm`), so file-browser's packaging prose — how *other* projects
102
+ * consume file-browser — stays out of scope, as it should be.
103
+ */
104
+ const STALE_PATTERNS = [
105
+ { pattern: /\bnpm run ldt\b/, label: '`npm run ldt`' },
106
+ { pattern: /\bnpm link\b/, label: '`npm link`' },
107
+ { pattern: /\bvolta run\b/, label: '`volta run`' },
108
+ { pattern: /\bllinks\b/, label: 'the `llinks` verify script' },
109
+ { pattern: /\bmust be re-run\b/, label: 'the after-install re-run instruction' },
110
+ { pattern: /\btypescript-sdk\b/, label: 'the retired `typescript-sdk` package name' }
111
+ ];
112
+
113
+ /**
114
+ * The one shape `collectReadmeDrift` returns per finding — same fields as the
115
+ * link-doctor's problems, so reporters can treat the two checks alike.
116
+ *
117
+ * @typedef {object} ReadmeFinding
118
+ * @property {'ldt section missing' | 'ldt section drift' | 'publish section missing' | 'publish section drift'} kind
119
+ * @property {string} pkg The package directory under `Frontend/`.
120
+ * @property {string} detail What is wrong, README-relative.
121
+ * @property {string} fix The action that repairs it.
122
+ */
123
+
124
+ /**
125
+ * Strip fenced code blocks and collapse wrapping, so sentence matching and
126
+ * stale-pattern scanning see prose the way a reader does. Fenced blocks are
127
+ * dropped entirely: the canonical section is prose, and instructions inside a
128
+ * fence are commands somebody is expected to run — exactly what must not
129
+ * sneak back. Link targets lose their `#fragment`: the anchor is navigation
130
+ * detail, not wording, and deep links to the workflow section are fine.
131
+ *
132
+ * @param {string} text A README's raw text.
133
+ * @returns {string} Prose with fences removed and runs of whitespace collapsed.
134
+ */
135
+ function prose(text) {
136
+ const kept = [];
137
+ let fenced = false;
138
+ for (const line of text.split('\n')) {
139
+ if (/^\s*```/.test(line)) {
140
+ fenced = !fenced;
141
+ continue;
142
+ }
143
+ if (!fenced) kept.push(line);
144
+ }
145
+ return kept
146
+ .join('\n')
147
+ .replace(/\]\(([^)\s#]+)#[^)\s]*\)/g, ']($1)')
148
+ .replace(/\s+/g, ' ')
149
+ .trim();
150
+ }
151
+
152
+ /**
153
+ * The first sentence of `sentences` that is missing or out of order, or
154
+ * `null` when the text carries all of them, in order.
155
+ *
156
+ * @param {string} text Whitespace-collapsed prose.
157
+ * @param {string[]} sentences The canonical sentences to require.
158
+ * @returns {string | null}
159
+ */
160
+ function firstMissingSentence(text, sentences) {
161
+ let at = 0;
162
+ for (const sentence of sentences) {
163
+ at = text.indexOf(sentence, at);
164
+ if (at === -1) return sentence;
165
+ at += sentence.length;
166
+ }
167
+ return null;
168
+ }
169
+
170
+ /** The stale link-era instructions present in the text, as readable labels. */
171
+ export function staleInstructionHits(text) {
172
+ return STALE_PATTERNS.filter(({ pattern }) => pattern.test(text)).map(({ label }) => label);
173
+ }
174
+
175
+ /**
176
+ * The `ldt section drift` finding for retired instructions in `text`, or none.
177
+ * Both tiers reach their prose this way, so the same drift reports the same
178
+ * way wherever it appears — only the repair differs, since an adopter's setup
179
+ * is already an ordinary `npm install` and a linking package's is not.
180
+ *
181
+ * @param {string} pkg The package's directory name under `Frontend/`.
182
+ * @param {string} text Whitespace-collapsed prose.
183
+ * @param {string} fix The action that repairs the drift.
184
+ * @returns {ReadmeFinding[]}
185
+ */
186
+ function staleFindings(pkg, text, fix) {
187
+ const stale = staleInstructionHits(text);
188
+ if (stale.length === 0) return [];
189
+ return [
190
+ {
191
+ kind: 'ldt section drift',
192
+ pkg,
193
+ detail: `link-era instructions present in the README: ${stale.join(', ')}`,
194
+ fix
195
+ }
196
+ ];
197
+ }
198
+
199
+ /**
200
+ * Find what one package's README violates, by tier: an adopter must carry the
201
+ * canonical sibling-source sentences (and a publisher the publish ones), while
202
+ * a linking package must only keep the retired instructions out of its prose.
203
+ * `readmePath` exists only for the error message when the file itself is
204
+ * absent — for an adopter a missing README is a missing section.
205
+ *
206
+ * @param {string} pkg The package's directory name under `Frontend/`.
207
+ * @param {string} readmePath Where the README should be.
208
+ * @param {string} raw The README's raw text, or `''` when absent.
209
+ * @returns {ReadmeFinding[]}
210
+ */
211
+ export function readmeFindings(pkg, readmePath, raw) {
212
+ const findings = [];
213
+ const text = prose(raw);
214
+
215
+ // A linking package carries no canonical section, so nothing about its
216
+ // prose is required to exist — only the retired instructions are banned.
217
+ if (LINKING_PACKAGES.includes(pkg)) {
218
+ return staleFindings(
219
+ pkg,
220
+ text,
221
+ 'retire the hand-linking instructions — this package links a sibling checkout by hand and has not adopted the dev-alias workflow yet (see dev-tools README, "The ldt workflow")'
222
+ );
223
+ }
224
+
225
+ const canonicalGap = text ? firstMissingSentence(text, CANONICAL_SENTENCES) : CANONICAL_SENTENCES[0];
226
+ if (canonicalGap !== null) {
227
+ // A README that names dev-tools has a section that drifted; one that
228
+ // never mentions it has no section to drift.
229
+ const drifted = text.includes('@widgetic/dev-tools');
230
+ findings.push({
231
+ kind: drifted ? 'ldt section drift' : 'ldt section missing',
232
+ pkg,
233
+ detail: drifted
234
+ ? `the sibling-source section does not carry the canonical prose — first sentence missing or out of order: "${canonicalGap}"`
235
+ : `no sibling-source section was found in ${readmePath}`,
236
+ fix: 'copy the canonical sibling-source section from dev-tools/README.md ("The ldt workflow"); keep app-specific notes outside its sentences'
237
+ });
238
+ // An absent README hides the publish requirement too — a publisher must
239
+ // hear about both sections, not just the first one found.
240
+ if (PUBLISH_PACKAGES.includes(pkg)) {
241
+ findings.push({
242
+ kind: 'publish section missing',
243
+ pkg,
244
+ detail: `no publish-preparation section was found in ${readmePath}`,
245
+ fix: 'copy the canonical publish-preparation sentences from dev-tools/README.md; keep app-specific flow notes outside them'
246
+ });
247
+ }
248
+ return findings;
249
+ }
250
+
251
+ findings.push(
252
+ ...staleFindings(
253
+ pkg,
254
+ text,
255
+ 'retire the link-era instructions; the workflow is an ordinary npm install (see dev-tools README, "The ldt workflow")'
256
+ )
257
+ );
258
+
259
+ if (PUBLISH_PACKAGES.includes(pkg)) {
260
+ const publishGap = text ? firstMissingSentence(text, CANONICAL_PUBLISH_SENTENCES) : CANONICAL_PUBLISH_SENTENCES[0];
261
+ if (publishGap !== null) {
262
+ // A section that shares any canonical wording has drifted; unrelated
263
+ // publishing prose (app-specific iteration notes say "publishing" too)
264
+ // is a missing section, not a drifted one.
265
+ const drifted = CANONICAL_PUBLISH_SENTENCES.some((s) => text.includes(s));
266
+ findings.push({
267
+ kind: drifted ? 'publish section drift' : 'publish section missing',
268
+ pkg,
269
+ detail: drifted
270
+ ? `the publish-preparation section does not carry the canonical prose \u2014 first sentence missing or out of order: "${publishGap}"`
271
+ : `no publish-preparation section was found in ${readmePath}`,
272
+ fix: 'copy the canonical publish-preparation sentences from dev-tools/README.md; keep app-specific flow notes outside them'
273
+ });
274
+ }
275
+ }
276
+
277
+ return findings;
278
+ }
279
+
280
+ /**
281
+ * Collect every README finding under a Frontend checkout.
282
+ *
283
+ * @param {string} frontendRoot The `Frontend/` checkout root.
284
+ * @param {{ packages?: string[] }} [options] Package directories to check;
285
+ * defaults to {@link CHECKED_PACKAGES} (both tiers).
286
+ * @returns {{ packages: string[], findings: ReadmeFinding[] }}
287
+ */
288
+ export function collectReadmeDrift(frontendRoot, { packages, adopters } = {}) {
289
+ // The option selected one tier's packages until there were two. Failing
290
+ // loudly beats the alternative: an old caller's list would be ignored and
291
+ // the defaults would be checked instead, which silently checks the wrong
292
+ // thing — the exact failure this package exists to prevent.
293
+ if (adopters !== undefined) {
294
+ throw new Error(
295
+ 'collectReadmeDrift: the `adopters` option was renamed to `packages` — it now selects both contract tiers'
296
+ );
297
+ }
298
+
299
+ const subjects = packages ?? CHECKED_PACKAGES;
300
+ const findings = [];
301
+ for (const pkg of subjects) {
302
+ const readmePath = `${frontendRoot}/${pkg}/README.md`;
303
+ const raw = existsSync(readmePath) ? readFileSync(readmePath, 'utf8') : '';
304
+ findings.push(...readmeFindings(pkg, readmePath, raw));
305
+ }
306
+ return { packages: [...subjects], findings };
307
+ }
@@ -0,0 +1,71 @@
1
+ /**
2
+ * The smallest semver range test this repo needs — `satisfies` for the range
3
+ * shapes the widgetic manifests actually declare: carets (`^0.5.12`),
4
+ * greater-than-or-equal peers (`>=0.3.0`), and exact pins (`0.5.14`).
5
+ *
6
+ * This deliberately replaces a `semver` dependency: the check ships to
7
+ * consumers through the dev-tools tarball, and the four lines of range logic
8
+ * below are the entire contract. Anything this cannot parse fails *closed* —
9
+ * `satisfies` returns `false` so an exotic range surfaces as a finding, not as
10
+ * a silent pass.
11
+ *
12
+ * @param {string} version A concrete version, e.g. `0.5.14`.
13
+ * @param {string} range A range specifier, e.g. `^0.5.12`.
14
+ * @returns {boolean} Whether `version` satisfies `range`.
15
+ */
16
+ export function satisfies(version, range) {
17
+ const v = parse(version);
18
+ if (!v) return false;
19
+
20
+ const spec = range.trim();
21
+ if (spec === '*' || spec === '') return true;
22
+
23
+ // Tolerate a leading `v`.
24
+ const body = spec.startsWith('v') ? spec.slice(1) : spec;
25
+
26
+ if (body.startsWith('^')) {
27
+ const base = parse(body.slice(1));
28
+ if (!base) return false;
29
+ // ^0.x.y behaves like ~0.x.y in semver: the leftmost nonzero digit is
30
+ // the ceiling. For 0.5.x that means minor must match.
31
+ if (base.major === 0) {
32
+ return v.major === 0 && v.minor === base.minor && v.patch >= base.patch;
33
+ }
34
+ return v.major === base.major && cmp(v, base) >= 0;
35
+ }
36
+
37
+ if (body.startsWith('>=')) {
38
+ const base = parse(body.slice(2));
39
+ return base ? cmp(v, base) >= 0 : false;
40
+ }
41
+
42
+ if (body.startsWith('>')) {
43
+ const base = parse(body.slice(1));
44
+ return base ? cmp(v, base) > 0 : false;
45
+ }
46
+
47
+ const exact = parse(body);
48
+ return exact ? cmp(v, exact) === 0 : false;
49
+ }
50
+
51
+ /**
52
+ * Parse `major.minor.patch` into numbers, or `null` for anything else —
53
+ * prerelease and build suffixes are outside this check's vocabulary on
54
+ * purpose: failing closed beats approximating.
55
+ *
56
+ * @param {string} s
57
+ * @returns {{ major: number, minor: number, patch: number } | null}
58
+ */
59
+ export function parse(s) {
60
+ const m = /^(\d+)\.(\d+)\.(\d+)$/.exec(String(s).trim());
61
+ if (!m) return null;
62
+ return { major: +m[1], minor: +m[2], patch: +m[3] };
63
+ }
64
+
65
+ /** Three-way compare of parsed versions. */
66
+ function cmp(a, b) {
67
+ for (const k of ['major', 'minor', 'patch']) {
68
+ if (a[k] !== b[k]) return a[k] < b[k] ? -1 : 1;
69
+ }
70
+ return 0;
71
+ }
package/package.json CHANGED
@@ -1,8 +1,8 @@
1
1
  {
2
2
  "name": "@widgetic/dev-tools",
3
- "version": "0.2.0",
3
+ "version": "0.3.0",
4
4
  "type": "module",
5
- "description": "Build-time checks and dev tooling shared by the published @widgetic packages, released once so the repositories that consume them cannot drift apart. Currently: check-runtime-deps (with the fixture suite that proves it fails), the Vite sibling-$lib remap, the canonical Frontend sibling layout that builds every consumer's dev-alias tables, and check-links — the link-doctor that fails when a sibling symlink dangles, a promised dist/ file is missing, or a dead checkout name lingers.",
5
+ "description": "Build-time checks and dev tooling shared by the published @widgetic packages, released once so the repositories that consume them cannot drift apart. Currently: check-runtime-deps (with the fixture suite that proves it fails), the Vite sibling-$lib remap, the canonical Frontend sibling layout that builds every consumer's dev-alias tables, and check-links — the link-doctor that fails when a sibling symlink dangles, a promised dist/ file is missing, or a dead checkout name lingers, and check-design-system-peers — which fails when the two design-system peers' lockfiles drift apart.",
6
6
  "repository": {
7
7
  "type": "git",
8
8
  "url": "git+https://gitlab.com/widgeticai/Frontend/dev-tools.git"
@@ -19,7 +19,10 @@
19
19
  "check-runtime-deps-fixtures": "bin/check-runtime-deps-fixtures.mjs",
20
20
  "check-links": "bin/check-links.mjs",
21
21
  "check-links-fixtures": "bin/check-links-fixtures.mjs",
22
- "check-layout-fixtures": "bin/check-layout-fixtures.mjs"
22
+ "check-readme-contracts": "bin/check-readme-contracts.mjs",
23
+ "check-readme-contracts-fixtures": "bin/check-readme-contracts-fixtures.mjs",
24
+ "check-layout-fixtures": "bin/check-layout-fixtures.mjs",
25
+ "check-design-system-peers": "bin/check-design-system-peers.mjs"
23
26
  },
24
27
  "files": [
25
28
  "bin",
@@ -34,8 +37,12 @@
34
37
  "test:layout": "node --test test/frontend-layout.test.mjs",
35
38
  "test:layout:disk": "node bin/check-layout-fixtures.mjs",
36
39
  "check:links": "node bin/check-links.mjs",
40
+ "check:readme": "node bin/check-readme-contracts.mjs",
41
+ "check:peers": "node bin/check-design-system-peers.mjs",
37
42
  "test:links": "node bin/check-links-fixtures.mjs",
38
- "test": "npm run check:deps && npm run test:deps && npm run test:vite && npm run test:layout && npm run test:links",
43
+ "test:readme": "node --test test/readme-contract.test.mjs",
44
+ "test:peers": "node --test test/lockfile-peers.test.mjs",
45
+ "test": "npm run check:deps && npm run test:deps && npm run test:vite && npm run test:layout && npm run test:links && npm run test:readme && npm run test:peers",
39
46
  "prepublishOnly": "npm test"
40
47
  },
41
48
  "volta": {