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
Copy file name to clipboardExpand all lines: README.md
+5-9Lines changed: 5 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,7 +44,7 @@ if (result) {
44
44
// result.html is a ready-made snippet
45
45
// or use result.title, result.summary, result.steps, result.patch, result.trace
46
46
} else {
47
-
// no friendly explanation — show the original traceback as-is
47
+
// no friendly explanation - show the original traceback as-is
48
48
}
49
49
50
50
// if the trace reports an unhelpful source location (eg. Pyodide runs code as "<exec>"), pass file explicitly to override what's parsed from the trace:
@@ -70,7 +70,7 @@ See the [demo](docs/README.md) for a full set of examples.
70
70
71
71
`result.html` is built to be accessible by default (with WCAG 2.1 AA in mind):
72
72
73
-
- The whole explanation is one labelled group —`<div class="pfem" role="group" lang="…" aria-labelledby="…">`, named by its title, with `lang` taken from the copydeck so screen readers pronounce localised copy correctly (`3.1.2 Language of Parts`). `role="group"` (not a landmark) keeps things uncluttered when several explanations render on one page
73
+
- The whole explanation is one labelled group:`<div class="pfem" role="group" lang="…" aria-labelledby="…">`, named by its title, with `lang` taken from the copydeck so screen readers pronounce localised copy correctly (`3.1.2 Language of Parts`). `role="group"` (not a landmark) keeps things uncluttered when several explanations render on one page
74
74
- The title is deliberately not a heading. Heading level depends on the surrounding page outline, which a library can't know, so the title supplies the group's accessible name instead. If you want it in your heading outline, render your own heading from `result.title` and use `result.html` (or the structured fields) for the body
75
75
- Code is marked up as code; inline tokens use `<code>` and blocks use `<pre><code>`
76
76
- The suggested fix has a visible "Suggested fix" label; the original traceback stays in a native `<details>`/`<summary>`
@@ -162,14 +162,10 @@ The script:
162
162
6. pushes the commits and tag, and
163
163
7. creates a GitHub Release with notes generated from the commits/PRs since the previous tag.
164
164
165
-
If `npm publish` fails, nothing is pushed — the script prints how to undo the local
165
+
If `npm publish` fails, nothing is pushed - the script prints how to undo the local
166
166
bump and retry.
167
167
168
168
### Prerequisites (one-time)
169
169
170
-
-`npm login` — publishing uses your local npm credentials (the package publishes
171
-
publicly via `publishConfig.access: "public"`).
172
-
-`gh auth login` — the GitHub Release is created with the `gh` CLI.
173
-
174
-
Tests still run automatically on every push to `main` and on pull requests via
0 commit comments