Winter is coming...

Wasmer

Last update: Oct 6, 2023

Related tags

Command-line winterjs

Overview

WinterJS

The JavaScript server that runs Service Workers according to the Winter Community Group specification.

Running WinterJS with Wasmer

The WinterJS server is published in Wasmer as wasmer/winter.

You can run the HTTP server locally with:

wasmer run wasmer/winter --net --mapdir=tests:tests tests/simple.js

Where simple.js is:

addEventListener('fetch', (req) => {
  return "hello";
});

Note: The interface that is provided to Service Workers can be seen in winter.d.ts.

Running WinterJS Natively

You can run WinterJS natively by simply doing

cargo run -- tests/simple.js

And then access the server in https://localhost:8080/

How WasmerJS works

Wasmer Winter is powered by SpiderMonkey and Axum to bring a new level of awesomeness to your Javascript apps.

To compile the app to WebAssembly WinterJS is using the WASIX standard.

Comments

Add typings to the project

I've created a winter.d.ts file which defines the interface exposed by our WinterJS implementation based on what I can infer from the code.

This PR also adds an example that shows how to write a WinterJS app in JavaScript.

opened by Michael-F-Bryan 0
Minimal WinterCG implementation
https://common-min-api.proposal.wintercg.org/

[ ] Blob

[ ] File

[ ] FormData

The FormData constructor optionally takes [HTMLFormElement (https://html.spec.whatwg.org/multipage/forms.html#htmlformelement) and [HTMLElement (https://html.spec.whatwg.org/multipage/dom.html#htmlelement) as parameters. TODO: Figure out what implementations without DOM support should do here. Node.js and Deno throw if the first parameter is not undefined but ignore the second parameter. Cloudflare Workers ignores all parameters.

[ ] Headers

[ ] Crypto

[ ] Request

[ ] Response

[ ] TextDecoder

[ ] TextDecoderStream

[ ] TextEncoder

[ ] TextEncoderStream

[ ] TransformStream

[ ] URL

[ ] URLSearchParams

[ ] WritableStream

https://w3c.github.io/ServiceWorker/#wait-until-method

Not yet:

[ ] Event

[ ] EventTarget

[ ] AbortController

[ ] AbortSignal

[ ] ByteLengthQueuingStrategy

[ ] CompressionStream

[ ] CountQueuingStrategy

[ ] CryptoKey

[ ] DecompressionStream

[ ] DOMException

[ ] ReadableByteStreamController

[ ] ReadableStream

[ ] ReadableStreamBYOBReader

[ ] ReadableStreamBYOBRequest

[ ] ReadableStreamDefaultController

[ ] ReadableStreamDefaultReader

[ ] SubtleCrypto

[ ] TransformStreamDefaultController

[ ] WebAssembly.Global

[ ] WebAssembly.Instance

[ ] WebAssembly.Memory

[ ] WebAssembly.Module

[ ] WebAssembly.Table

[ ] WritableStreamDefaultController
opened by syrusakbary 0
Implement URL Class

The spec uses the URL class in multiple places for requests/responses.

Need to add that class and use it in all required places. (request/response class fields, support for supplying a URL as first fetch param, etc).

Two ways to go: use a Rust class, or just use one of the available Javascript polyfills and add them to the setup.js code.
bug

opened by theduke 1
Full fetch implementation
Implement a full fetch implementation.

Full here means:

sending headers

setting timeouts

receiving body and headers

Initially we can punt on streaming request and response bodies, like we did for the server requests/responses, but this must then be done as a followup. (create followup issue if not in initial implementation!)

Should have some tests running against a local mock hyper server to validate full functionality.
enhancement
opened by theduke 0
Investigate High CPU Load and Server Stalling In WASIX

When running in WASIX, the server has very high CPU usage, and stops responding to requests after a short time (1 minute or so).

This might be related to setting up multiple runtimes, and hence could be fixed by #1 , but this needs to be investigated.
bug

opened by theduke 0

Owner

Wasmer

The Universal WebAssembly Runtime. We ❤️ Open Source

GitHub

Druid Exporter plays a fundamental role as a receiver of metrics events coming from Druid clusters, adopting the HTTP format as a means of communication

Druid Exporter plays a fundamental role as a receiver of metrics events coming from Druid clusters, adopting the HTTP format as a means of communication. In addition to this capability, its primary function is to export these metrics to Prometheus, thus allowing the creation of meaningful graphs and visualizations.

3 Sep 21, 2023

Druid Exporter plays a fundamental role as a receiver of metrics events coming from Druid clusters, adopting the HTTP format as a means of communication.

5 Oct 24, 2023