@replayio/node
Advanced tools
CLI tool for creating recordings using the Replay version of node.
The replay version of node is a replacement for the node executable which saves a recording of its behavior to disk that can be uploaded to the record/replay web service for viewing. replay-node is a CLI tool that allows the replay version of node to be selectively used when running node scripts.
npm i @replayio/node --global
replay-node can be used in the following ways to create recordings. Afterwards, use the @replayio/replay CLI tool to manage and upload the recordings.
replay-node script.js ...args
Use the replay version of node to record a specific script and arguments.
replay-node --exec executable ...args
Run an executable command with $PATH updated so that all node scripts will use the Replay version of node to record their behavior.
replay-node --update
Ensure the replay version of node is downloaded/updated.
node binary is to be found.recordreplay.so driver library.FAQs
CLI tool for creating recordings using the replay version of node
The npm package @replayio/node receives a total of 2 weekly downloads. As such, @replayio/node popularity was classified as not popular.
We found that @replayio/node demonstrated a healthy version release cadence and project activity because the last version was released less than 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.
Research
Security News
Socket researchers uncover the risks of a malicious Python package targeting Discord developers.
Security News
The UK is proposing a bold ban on ransomware payments by public entities to disrupt cybercrime, protect critical services, and lead global cybersecurity efforts.
Security News
Snyk's use of malicious npm packages for research raises ethical concerns, highlighting risks in public deployment, data exfiltration, and unauthorized testing.