Changelog

0.6.0 (2023-12-21)

The @wasmer/sdk Runtime has removed the limit on the maximum number of worker threads it is allowed to spawn. The corresponding poolSize option has been removed from RuntimeOptions.

The @wasmer/sdk Runtime has removed the limit on the maximum number of worker threads it is allowed to spawn. The corresponding poolSize option has been removed from RuntimeOptions. (d5da4ea)

Bumped the virtual-fs dependency so we get a non-buggy StaticFile implementation (fixes #366) (47b4633)
Made sure users still get typings whenever they import a file from dist/ (956d404)
Update the OptionOptions type definition to accept Uint8Array as stdin, rather than ArrayBuffer (a1d4045)

Renamed Wasmer.fromWebc() to Wasmer.fromFile()
Renamed Output.stdoutUtf8 and friends to make the more common use case shorter
Importing @wasmer/sdk will now use the smaller, non-embedded bundle by default
- This should improve page load times for end users by being more cache-friendly and not needing to download/parse a ~6MB *.js file on startup
- Users will need to explicitly import @wasmer/sdk/dist/WasmerSDKBundled.js if they want the old behaviour
- Users may need to call setWorkerUrl() to point at wasmer_js_bg.wasm

Renamed Output.stdoutUtf8 and friends to make the more common use case shorter (f94cc58)
The package now includes dist/WasmerSDKBundled.* files which embed the compiled Rust code as a base64 string as well as dist/WasmerSDK.* files which load the Rust code from the server as a *.wasm binary at runtime (75c4bf1)
Importing @wasmer/sdk will now use the smaller, non-embedded bundle by default (75c4bf1)

A warning will now be emitted when the @wasmer/sdk package is loaded outside of a Cross-Origin Isolated context (4dc5799)
Errors encountered when the scheduler handles a message are now logged at the error level so they get printed by default (c5decb5)
Mitigated a race condition in the thread pool by marking workers as "busy" when they are sent blocking tasks, rather than when the tasks are received (35292d8)
The UMD module now exposes @wasmer/sdk under the name, WasmerSDK, rather than Library (d34bb7a)

The Output you get from await instance.wait() now contains stdoutUtf8 and stderrUtf8 fields with stdout/stderr lazily parsed as UTF-8 strings (61f3319)

Resolved an issue where constructing a Directory with a DirectoryInit containing a nested file would error out while creating the file's parent directory (f45f561)
Resolved an unconditional panic when passing a DirectoryInit to Command.spawn() or runWasix()'s mount argument (50df67d)

Removed the Container, Manifest, and Volume types
Functionality needing a Runtime will now use a lazily initialized global runtime if one wasn't provided
Renamed SpawnConfig and RunConfig to SpawnOptions and RunOptions.

A Wasmer package now has a commands field which maps a Command's name to its instance (243d4b9)
A Wasmer package now has an entrypoint field with a runnable Command (243d4b9)
Added a Command.binary() method for accessing the binary run by a Command (243d4b9)
Added a Wasmer.fromWebc() constructor for loading a *.webc file (4606724)
Functionality needing a Runtime will now use a lazily initialized global runtime if one wasn't provided (70a2083)
Introduced a DirectoryInit type that lets you initialize a Directory with a map from file paths to their contents (553ded5)
Rewrote the top-level Wasmer type to represent a package that has been loaded and is ready for execution (9f54cb5)
Users are now able to mount directories using either a existing Directory or a DirectoryInit which will be used to instantiate a new Directory (e43ea8c)

Removed the Container, Manifest, and Volume types (e2ed292)
Renamed SpawnConfig and RunConfig to SpawnOptions and RunOptions. (e43ea8c)

Users can now mount a Directory (backed by an in-memory filesystem) when spawning WASIX instances (98e5d92)

The logger will now proxy all messages to the main thread so output from Web Workers can be captured (dba73fd)