A high-performance JavaScript server that runs Service Workers scripts compliant with the WinterCG specification.
WinterJS is a high-performance JavaScript server runtime that executes Service Workers scripts according to the WinterCG specification. It is designed for server-side applications requiring fast request handling, leveraging SpiderMonkey and hyper to achieve up to 100,000 requests per second on a single laptop. It solves the need for a standards-compliant, performant JavaScript runtime for edge and server environments.
Developers building high-throughput server-side applications, edge computing services, or those needing a WinterCG-compliant JavaScript runtime. It is also suitable for projects requiring WebAssembly deployment via WASIX.
Developers choose WinterJS for its exceptional performance and adherence to the WinterCG specification, ensuring compatibility with standardized web APIs. Its ability to compile to WebAssembly via WASIX offers deployment flexibility, while its focus on Service Workers makes it ideal for event-driven server logic.
Winter is coming... ❄️
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Benchmarks show it handles up to 100,000 requests per second on a single laptop, making it ideal for high-throughput server applications.
Implements the WinterCG specification with stable APIs like fetch, URL, and Response, ensuring compatibility with standardized server-side JavaScript.
Runs Service Workers scripts for event-driven server logic, similar to edge computing platforms like Cloudflare Workers.
Can be compiled to WebAssembly using WASIX, enabling sandboxed execution in Wasmer environments for added security and flexibility.
The project is now deprecated in favor of Edge.js, meaning no future updates, bug fixes, or official support, making it risky for production use.
Building from source requires setting up SpiderMonkey with additional dependencies, as per the README, which can be time-consuming and error-prone.
Some WinterCG APIs are only partially implemented, such as TransformStream lacking back-pressure and crypto.subtle supporting only HMAC, MD5, and SHA algorithms.
The caches API is memory-backed, so cached responses do not persist between server restarts, limiting its usefulness for stateful applications.