base on Winter is coming... ❄️ <div align="center"> <a href="https://github.com/wasmerio/winterjs" target="_blank"> <picture> <source srcset="https://raw.githubusercontent.com/wasmerio/winterjs/main/assets/winterjs-logo-white.png" height="128" media="(prefers-color-scheme: dark)"> <img height="128" src="https://raw.githubusercontent.com/wasmerio/winterjs/main/assets/winterjs-logo-black.png" alt="Wasmer logo"> </picture> </a> </div> WinterJS is *blazing-fast* JavaScript server that runs Service Workers scripts according to the [Winter Community Group specification](https://wintercg.org/). **WinterJS is able to handle up to 100,000 reqs/s in a single laptop** (see [Benchmark](./benchmark)). ---- > Note: WinterJS is not officially endorsed by WinterCG, despite sharing "Winter" in their name. There are many [runtimes supporting WinterCG](https://runtime-keys.proposal.wintercg.org/), WinterJS being one among those. ## Running WinterJS with Wasmer The WinterJS server is published in Wasmer as [`wasmer/winterjs`](https://wasmer.io/wasmer/winterjs). You can run the HTTP server locally with: ```shell wasmer run wasmer/winterjs --net --mapdir=tests:tests tests/simple.js ``` Where `simple.js` is: ```js addEventListener('fetch', (req) => { req.respondWith(new Response('hello')); }); ``` ## Building from source WinterJS needs to build SpiderMonkey from source as part of its own build process. Please follow the steps outlined here to make sure you are ready to build SpiderMonkey: https://github.com/wasmerio/mozjs/blob/master/README.md. You also need to do this before installing WinterJS with `cargo install`, which builds WinterJS from the source instead of downloading pre-built binaries. Also, when building WinterJS in debug mode, you need to have NodeJS and npm installed and run `npm install` beforehand. This is required since debug builds of WinterJS also build the TypeScript code in `src/builtins/internal_js_modules`. Release builds use the existing, pre-compiled `*.js` sources in that directory. This was done to simplify installing WinterJS with `cargo install`. If you update the TypeScript sources, make sure to update the `*.js` sources by building at least once in debug mode and commit the updated `*.js` files. Once you can build SpiderMonkey, you simply need to run `cargo build` as usual to build WinterJS itself. ## Running WinterJS Natively You can install WinterJS natively with: ``` cargo install --git https://github.com/wasmerio/winterjs winterjs ``` Once you have WinterJS installed, you can simply do: ```shell winterjs tests/simple.js ``` And then access the server in https://localhost:8080/ # How WinterJS works WinterJS is powered by [SpiderMonkey](https://spidermonkey.dev/), [Spiderfire](https://github.com/Redfire75369/spiderfire) and [hyper](https://hyper.rs/) to bring a new level of awesomeness to your Javascript apps. WinterJS is using the [WASIX](https://wasix.org) standard to compile to WebAssembly. Please note that compiling to WASIX is currently a complex process. We recommend using precompiled versions from [`wasmer/winterjs`](https://wasmer.io/wasmer/winterjs), but please open an issue if you need to compile to WASIX locally. ## Limitations WinterJS is fully compliant with the WinterCG spec, although the runtime itself is still a work in progress. For more information, see the API Compatibility section below. # WinterCG API Compatibility This section will be updated as APIs are added/fixed. If an API is missing from this section, that means that it is still not implemented. You can check a more detailed list here: https://runtime-compat.unjs.io/ The following words are used to describe the status of an API: * ✅ Stable - The API is implemented and fully compliant with the spec. This does not account for potential undiscovered implementation errors in the native code. * 🔶 Partial - The API is implemented but not fully compliant with the spec and/or there are known limitations. * ❌ Pending - The API is not implemented yet. |API|Status|Notes| |:-:|:-:|:--| |`console`|✅ Stable| |`fetch`|✅ Stable| |`URL`|✅ Stable| |`URLSearchParams`|✅ Stable| |`Request`|✅ Stable| |`Headers`|✅ Stable| |`Response`|✅ Stable| |`Blob`|✅ Stable| |`File`|✅ Stable| |`FormData`|✅ Stable| |`TextDecoder`|✅ Stable| |`TextDecoderStream`|✅ Stable| |`TextEncoder`|✅ Stable| |`TextEncoderStream`|✅ Stable| |`ReadableStream` and supporting types|✅ Stable| |`WritableStream` and supporting types|✅ Stable| |`TransformStream` and supporting types|🔶 Partial|Back-pressure is not implemented |`atob`|✅ Stable| |`btoa`|✅ Stable| |`performance.now()`|✅ Stable| |`performance.timeOrigin`|✅ Stable| |`crypto`|✅ Stable| |`crypto.subtle`|🔶 Partial|Only HMAC, MD5 and SHA algorithms are supported # Other supported APIs The following (non-WinterCG) APIs are implemented and accessible in WinterJS: |API|Status|Notes| |:-:|:-:|:--| |[Service Workers Caches API](https://www.w3.org/TR/service-workers/#cache-objects)|✅ Stable|Accessible via `caches`. `caches.default` (similar to [Cloudflare workers](https://developers.cloudflare.com/workers/runtime-apis/cache/#accessing-cache)) is also available.<br/>The current implementation is memory-backed, and cached responses will *not* persist between multiple runs of WinterJS. ", Assign "at most 3 tags" to the expected json: {"id":"4320","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"