
Research
Node.js Fixes AsyncLocalStorage Crash Bug That Could Take Down Production Servers
Node.js patched a crash bug where AsyncLocalStorage could cause stack overflows to bypass error handlers and terminate production servers.
stream-closer
Advanced tools
A CLI tool for stopping RS streams
brew install ffmpegnpm install -g stream-closer
You'll need your RS api token to use this tool. You can access it here: https://fot.reactive.live/admin/users/apitoken/
Close all streams:
stream-closer --token :your-rs-api-token
Close streams with a give tag:
stream-closer --token :your-rs-api-token -tag :your-tag
You can group your streams by giving them a tag. This, amoung other uses, will allow you to only close a targeted subset of streams. You can tag your streams at creation with a request like:
fetch(`https://fot.reactive.live/api/v1/streams/`, {
method: "POST",
headers: {
"Content-Type": "application/json",
Authorization: "Token :your-token",
},
body: JSON.stringify({ tag: "your-tag" }),
});
FAQs
An easy way to close streams on RS
The npm package stream-closer receives a total of 0 weekly downloads. As such, stream-closer popularity was classified as not popular.
We found that stream-closer demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer 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
Node.js patched a crash bug where AsyncLocalStorage could cause stack overflows to bypass error handlers and terminate production servers.

Research
/Security News
A malicious Chrome extension steals newly created MEXC API keys, exfiltrates them to Telegram, and enables full account takeover with trading and withdrawal rights.

Security News
CVE disclosures hit a record 48,185 in 2025, driven largely by vulnerabilities in third-party WordPress plugins.