Idea: complement tsdown reproduction links with a deterministic bug bundle

[zhou-wang-git]

Hi tsdown maintainers — your bug form makes a StackBlitz or GitHub minimal reproduction the most important requirement. I maintain BugBundle, an early-stage CLI intended to complement that workflow for failures involving local environments, watch mode, package metadata, or command output.

BugBundle does not replace or automatically minimize a reproduction repository. It creates a deterministic ZIP with a versioned manifest, the failing command and result, bounded/redacted logs, runtime metadata, and only explicitly allowlisted files. It stays offline, uploads nothing, and verification does not execute code.

Would you be open to trying it on one future tsdown report and telling me whether the artifact adds useful evidence beyond the reproduction link?

npx bugbundle@0.3.0 preview
npx bugbundle@0.3.0 capture --output bugbundle.zip -- pnpm test
npx bugbundle@0.3.0 inspect bugbundle.zip

The reporter must review the allowlist and complete ZIP before sharing it. I would especially value criticism about missing metadata, contributor friction, and where the privacy boundary remains unclear.

Disclosure: BugBundle is developed with Codex under maintainer review. This is a request for a one-issue design pilot, not an endorsement request.