Quickstart

Before you beginCopy Anchor Link

Complete installation and organization access. This example uses Node.js and a synthetic bug. It requires an interactive terminal, an internet connection, and available capture allowance in your organization.

Create a small exampleCopy Anchor Link

From a parent directory where you keep disposable projects:

mkdir reprolane-example
cd reprolane-example
npm init -y

You are now in reprolane-example. Create failure.cjs in this directory:

throw new Error("Expected checkout total 20, received 0");

From reprolane-example, run:

node failure.cjs

Expect the error above and a nonzero exit status. This example has no dependencies or external services.

Capture the failureCopy Anchor Link

Still in reprolane-example, run:

reprolane capture command "node failure.cjs" \
  --title "Checkout total is zero" \
  --expected "Checkout total is 20" \
  --actual "Checkout total is 0"

Reprolane freezes the source before running the command and collects the failure evidence. A failing captured command is expected. A successful CLI exit means capture and upload succeeded, not that your bug disappeared.

Review before uploadCopy Anchor Link

Read the effective privacy policy and destination organization. Review the selected files and sanitized previews. For this example, expect failure.cjs and package.json among the source files, plus the captured error output.

Only approve material you intend to share with people who can access the reproduction. Cancel if the destination or contents are wrong. Redaction cannot guarantee that every secret or private detail is removed. See upload review.

Open the reproductionCopy Anchor Link

After upload succeeds, the CLI prints a reproduction URL. Open it while signed in to an authorized account. Check the source, output, and stack frames against the error you just ran.

You have captured local evidence. When the app reports that replay is eligible, you can separately request verification. Capture alone does not run clean verification.

If something goes wrongCopy Anchor Link

If no URL appears, read the CLI error before retrying. Check organization and login settings, capture allowance, and upload review. If the command unexpectedly succeeds, check that you saved failure.cjs in the current directory.

Continue with command capture for your own application, or learn the core concepts.