You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit f413cd0
Browse filesBrowse the repository at this point in the historyBrowse files
lint: node --check runs in parallel (#261); its syntax-only scope is documented (#260)
lint drops from about 1.6 s to 0.8 s here. Undefined names still pass lint;
the header and CONTRIBUTING now say so, and that tests are what catch them.
Closes#260Closes#261
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LpkeXQPaUhxjgqdqnk6BrJ
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,7 +72,7 @@ To add a starter stack (one pick per need for a kind of game), follow [`stacks/R
72
72
73
73
Every pull request, every push to `main` (before the site deploys) and every release run one sequence, `npm run check` in [`package.json`](package.json). Pull requests and pushes run it on Node 24 and again on Node 22; releases run it on Node 24:
74
74
75
-
1.`npm run lint` (`site/lint.mjs`): every script parses, and none imports a name it does not use.
75
+
1.`npm run lint` (`site/lint.mjs`): every script parses, and none imports a name it does not use. It is syntax-only, not ESLint: a misspelled variable still passes and fails only when that line runs, so code the tests never reach needs a test or a careful read.
76
76
2.`npm test`: the checks against known-bad fixtures (`site/checks.test.mjs`) and the site modules' tests (`site/lib/lib.test.mjs`).
77
77
3.`npm run validate` (`site/validate.mjs`): every entry, link, count table and file against the checks.
78
78
4.`npm run check-added` (`site/check-added.mjs`): no entry's `added` date is later than the file's first commit, following renames. It needs the full git history; CI fetches it, and a shallow clone of your own will fail this step.
0 commit comments