Requires Node.js 22.12+ and npm. The published version used here is 1.5.0. Review the 1.5.0 changes and compatibility notes when upgrading.
npx --yes failtrace@1.5.0 demoThis does not put a permanent failtrace command on your shell's PATH. Continue using npx --yes failtrace@1.5.0 <command>, or choose an installation below. npm can download the package on first use; subsequent invocations normally use its cache.
npm install --save-dev failtrace@1.5.0
npx failtrace demoKeep the dependency and lockfile with your project. Target commands need their own dependencies and setup. The project itself need not use JavaScript.
For an existing npm project, name the baseline and verification actions to reuse the same conditions without retyping the flags.
npm install --global failtrace@1.5.0
failtrace demoFor native Windows applications that do not resolve npm's shims automatically, use failtrace.cmd or npx.cmd. Shell syntax inside a target command remains platform-specific.
The CLI and MCP server ship in the same package. Follow the MCP client setup guide. The configured client launches the stdio server; directly running failtrace mcp waits for protocol messages.
The verified v1.5.0 archive and checksum include compiled code:
npm exec --yes --allow-remote=root --package=https://github.com/LBarimi/FailTrace/releases/download/v1.5.0/failtrace-1.5.0.tgz -- failtrace demoThe command-scoped --allow-remote=root permits the explicitly requested URL on npm 12. Registry installation does not need this flag, and the command does not change npm's persistent configuration. Older npm versions that do not recognize it can omit it. See npm's URL install policy.
Before upgrading an existing integration, read the compatibility contract and migration guide.