Repository navigation
v0.4.0 — lower install barrier: one-step source install, Node 22+ baseline, config fix - #4
Merged
Merged
Conversation
…eline - Vitest 4+ removed `test.poolOptions`. Replace `poolOptions.forks.singleFork` with top-level `maxWorkers: 1`; `isolate` stays at its default so per-file test isolation is unchanged. Full suite re-run: 137/137, deprecation warning gone. - Node baseline: Node 18 (EOL Apr 2025) and Node 20 (EOL Mar 2026) are past end-of-life. Set engines to >=22 and align README (en/zh), installation and compatibility docs + the CI matrix to the supported, CI-tested LTS lines 22 & 24. - Add `prepare: npm run build` so installing from source (git / folder / npm pack) compiles dist/ automatically; this makes `npm i -g github:…#tag` actually work (it previously shipped unbuilt TS with no dist) and removes a manual build step from the quick start. Verified: a clean source install rebuilds dist and the CLI runs. npm remains unpublished (registry 404) — GitHub path stays the documented channel.
…uick-start `reprocase doctor` still treated Node 18/20 as acceptable while package.json now requires >=22 — the two must agree. checkNode now reports ok only on >=22 and a clear actionable failure below it (Node 18/20 are End-of-Life). The README quick-start (en/zh) drops the now-automatic `npm run build` (npm install runs `prepare`), reducing the first-run to clone -> install -> chromium -> demo. Verified: doctor healthy + exit 0 on Node 24; product doctor test green; full suite 137/137.
Regenerated report-desktop / report-finding / report-mobile PNGs by rendering the v0.4.0 CLI demo report in headless Chromium (deviceScaleFactor 1 to keep the repo lean). The per-finding card capture proves the report renders live content, not a blank page.
Bump 0.3.3 -> 0.4.0. CHANGELOG records the adoption-focused changes (Node 22+ baseline, one-step source install via prepare, deprecated Vitest poolOptions fix, independent-app accuracy validation). Update README (en/zh) Status and the compatibility matrix (137/137 on Node 22 & 24, v0.4.0). docs-consistency green.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adoption-focused release on the verified v0.3.3 base. No new detection rules; no UI rebuild.
npm installbuilds dist/ andnpm i -g github:…#tagactually works (previously shipped unbuilt TS). Quick start drops the manual build. Verified: clean source install rebuilds dist and runs.All security constraints + legacy regressions preserved (net/report/attachment/authorization 52 tests green). This PR's 4-platform CI also validates the Node 22 & 24 matrix.
Head: 3690cab