Repository navigation
Releases
Releases · omachala/heroshot
heroshot@0.19.4
Patch Changes
- e8a5a75: Fix
Something went wrongcrash onheroshot configin the standalone binary. The README template was read from disk at runtime, but Bun's compile step didn't bundle thetemplates/directory into the binary's virtual filesystem, so the first capture/config command crashed withENOENT: ... /$bunfs/root/templates/heroshotReadme.txt. Template is now inlined as a TypeScript constant so it ships with the binary.
heroshot@0.19.3
Patch Changes
- 9cbc16f: Fix two issues that made the CLI hard to use:
- MCP tool schemas were empty:
tools/listadvertisedproperties: {}for every tool, andheroshot_add/heroshot_removerejected valid input because arguments were silently dropped before reaching the handler. Tools now register their Zod schemas via the MCP SDK's native shape form, so inputs are parsed and forwarded correctly. - Errors surfaced as "Something went wrong": thrown errors during sync, config, or one-shot capture were caught by the spinner's exit hook and replaced with a generic message, often with exit code 0. The CLI now prints the actual error to stderr and exits with code 1. Use
--verbosefor the full stack trace.
- MCP tool schemas were empty:
heroshot@0.19.2
Patch Changes
- 090950b: Complete the standalone binary startup fix: Playwright also reads
browsers.jsonfrom its install dir at load time, which (likepackage.json) baked the build machine's absolute path into the binary and crashed on any other machine. Both files' contents are now inlined at build time. The CI binary smoke test (which runs each binary withnode_modulesremoved) caught this case that release 0.19.1's binaries missed.
heroshot@0.19.1
Patch Changes
- c667a51: Fix standalone binaries crashing on startup with "Cannot find module '.../playwright-core/package.json'". The Bun build baked the build machine's absolute path into the binary because the Playwright patch targeted an outdated playwright-core file layout and silently stopped applying after a Playwright upgrade. The patch now targets the current layout, derives the version dynamically, and fails the build if it no longer matches. CI also smoke-tests each built binary with
node_modulesremoved so this can't ship broken again.
heroshot@0.19.0
Minor Changes
- 7e64c4c: Add
heroshot mcpsubcommand that starts the MCP (Model Context Protocol) server over stdio. This lets you wire MCP-enabled agents (Claude Code, Cursor, Windsurf, VS Code Copilot) to the standalone binary from GitHub Releases, with no Node.js required — useful for CI runners, Docker images, and restricted environments.
heroshot@0.18.0
Minor Changes
- 180291a: Add
--ignore-https-errorsCLI flag andbrowser.ignoreHTTPSErrorsconfig option to capture local HTTPS endpoints with self-signed or untrusted certificates (e.g. Vitehttps: true, mkcert, Docker-proxied dev apps). Maps to Playwright'signoreHTTPSErrorsbrowser context option.
heroshot@0.17.0
Minor Changes
- f079600: Add native i18n locale support:
localesconfig option generates screenshots for multiple languages. Use{locale}in screenshot URLs for path-based routing. Sets browser locale and Accept-Language header per locale. Multiple locales output to{locale}/subdirectories; single locale preserves flat structure.
heroshot@0.16.0
Minor Changes
- 4664d80: Dependency updates and internal build improvements
heroshot@0.15.0
heroshot@0.14.2
Patch Changes
- 2dd9e04: fix(integrations): ensure generatePath produces absolute paths for framework components