An offline, read-only comparison of exported server HTML and a separately captured local render snapshot for configured essential headings, text and links. The tool never opens a browser, fetches a page, runs scripts, or changes a site. Its result is limited by the completeness and trustworthiness of the supplied capture.
This walkthrough uses the tool's public README and checked-in example files. Run the command from a repository checkout with Node.js 22+; inspect the source before using it on your own files.
Run the checked-in example
node bin/client-only-rendering-detector.mjs --root examples/passing --server server.html --render render.json --config config.json
node bin/client-only-rendering-detector.mjs --root examples/failing --server server.html --render render.json --config config.json
npm run checkRead the result
The passing command exits 0; the failing command exits 1 with client-only-essential for the first configured item. Use --out report.json to save the same JSON report in the evidence root, or --human for a short stderr summary. The JSON report is always sent to stdout unless output destination validation fails. Bad CLI configuration and refused output destinations exit 2 with empty stdout.
Where this check stops
This local walkthrough does not establish the state of a live production system or replace the limits documented in the repository.
Before adapting the command to your own workflow, review the accepted inputs, exit codes and safety boundaries in the README.
Compiled with AI assistance from checked-in public documentation and example scripts. Run the example and review the repository's current documentation before relying on its result.