
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.
glslify-api
Advanced tools
An API and accompanying client for generating glslify shaders in the browser
An API and accompanying client for generating glslify shaders in the browser.
This is done by running glslify in the browser, but redirecting its functions to read and resolve modules to a thin server. Files are cached locally using level.js to speed up the bundling speed after the first run – it can even work offline after downloading the required package once!
See the example directory for a simple example.
handle = api([cachedir])Returns an express-style route handler. cachedir is the location to store
temporary packages (using npm-file),
and defaults to .glslify.
handle(req, res, next)Given a request and response pair, handle a route. Will call next if there
is an error or a appropriate route is not found.
getShader = api(serverURI, [options])Returns a function for compiling shaders within the browser. serverURI
should be the URI where you're hosting your copy of the glslify-api server –
if you don't pass one in that's OK too, there's one being hosted at
glslify.shader.club.
Available options:
ttl: the maximum amount of time to cache a file locally, in milliseconds.getShader(source, done(err, result))Pass in a shader body source, and done will be called with either an error
or the glslified shader when ready.
GET /Should return:
{
"glslify": true
}
POST /-/shaderPipe a whole shader to the request body and get a glslified shader in return. This is a little more blunt than the approach in the client, but can be useful for small, quick experiments.
GET /:package/:file...Returns the raw contents of file from the package package on npm.
MIT. See LICENSE.md for details.
FAQs
An API and accompanying client for generating glslify shaders in the browser
We found that glslify-api 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.