v1.1.1

• Fix: Dynamic modules no longer import invoke unless they need to because they have additional exported functions

v1.1.0

• Added support for exporting JavaScript functions with no arguments and no return values from the generated Wasm module when provided with a WIT file and WIT world describing the name of the exported functions

v1.0.1

Fixes two bugs:

• Math.random() now uses the runtime's WASI context to seed the RNG so outputs from Math.random() are now random
• JavaScript code that fails to evaluate no longer results in a Rust panic being printed to stderr, instead a log message containing details about the JS error will be printed to stderr and a Wasm trap will be triggered

v1.0.0

What's Changed

There are no user facing changes, just library updates. We're confident that the Javy CLI is in good enough shape for general use so we're releasing it as v1.0.0.

Full Changelog: v0.6.0...v1.0.0

v0.6.0

What's Changed

• Reduce the number of host calls when logging by @jeffcharles in #279
• [Breaking] Error if there are pending items on the event queue by @jeffcharles in #277

Full Changelog: v0.5.3...v0.6.0

v0.5.3

What's Changed

• Compile JS source code as module instead of as global
• Linux binaries dynamically link against older version of glibc which should enable binaries to run on a wider variety of Linux systems

Full Changelog: v0.5.2...v0.5.3

v0.5.2

What's Changed

• Handle null byte in error message better by @jeffcharles in #225
• chore: Update wasi-sdk to version 19.0 by @saulecabrera in #237
• Return error when JS_Eval fails by @jeffcharles in #258
• Arm64 for Linux release asset

Full Changelog: v0.5.1...v0.5.2

v0.5.1

What's Changed

• Fix publish to upload wizened artifact by @jeffcharles in #222
• Improve javy npm cli wrapper by @surma in #220

v0.5.0

What's Changed

• Attach gzipped dylib as part of publishing by @jeffcharles in #201
• Add new CLI flag to emit provider binary by @surma in #205

v0.4.0

Bump version