@recordreplay/recordings-cli
Advanced tools
CLI tool for managing and uploading Replay recordings.
When using the Replay versions of node, playwright, or puppeteer, recordings which are created are saved to disk, by default in $HOME/.replay. This CLI tool is used to manage these recordings and upload them to the record/replay web service so that they can be viewed.
npm i @recordreplay/recordings-cli --global
replay-recordings <command>
Possible commands are given below. These may be used with the --directory <dir> option to override the default recording directory, or --server <address> to override the default server address.
View information about all known recordings. Prints a JSON array with one descriptor element for each recording. Recording descriptors have the following required properties:
id: ID used to refer to this recording in other commands.createTime: Time when the recording was created.runtime: Runtime used to create the recording: either gecko, chromium, or node.metadata: Any information the runtime associated with this recording. For gecko/chromium recordings this is the URI of the first page loaded, and for node recordings this is the original command line arguments.status: Status of the recording, see below for possible values.The possible status values for a recording are as follows:
onDisk: The recording was fully written out to disk.uploaded: The recording was fully uploaded to the record/replay web service.startedWrite: The recording started being written to disk but wasn't finished. Either the recording process is still running, or the recording process was killed and didn't shut down normally.startedUpload: The recording started being uploaded but didn't finish.unusable: The recording was marked as unusable for some reason, such as a stack overflow occurring.crashed: The recording process crashed before finishing.Depending on the status the recording descriptor can have some of the following additional properties:
path: If the recording started being written to disk (including before being uploaded), the path to the recording file.server: If the recording started being uploaded, the address of the server it was uploaded to.recordingId: If the recording started being uploaded, the server-assigned ID for this recording which can be used to view it.unusableReason: If the recording is unusable, the reason it was marked unusable.Upload the recording with the given ID to the web service.
Upload all recordings to the web service which can be uploaded.
Remove the recording with the given ID and any on disk file for it.
Remove all recordings and on disk recording files.
FAQs
CLI tool for uploading and managing recordings
The npm package @recordreplay/recordings-cli receives a total of 23,303 weekly downloads. As such, @recordreplay/recordings-cli popularity was classified as popular.
We found that @recordreplay/recordings-cli demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 7 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
A supply chain attack on Rspack's npm packages injected cryptomining malware, potentially impacting thousands of developers.
Research
Security News
Socket researchers discovered a malware campaign on npm delivering the Skuld infostealer via typosquatted packages, exposing sensitive data.
Security News
Sonar’s acquisition of Tidelift highlights a growing industry shift toward sustainable open source funding, addressing maintainer burnout and critical software dependencies.