Isomorphic library to handle passing high-level data structures between AssemblyScript and JavaScript. 🤝🚀

Markdown Parser Demo

• Features
• Installation
• Quick Start
• Additional Examples
• Supported Data Types
• Supported AssemblyScript Runtime Variants
• Reference API
• Motivation
• Performance
• Projects using as-bind
• FAQ and Common Issues
• Contributing
• License

• The library is Isomorphic. Meaning it supports both the Browser, and Node! And has ESM, CommonJS, and IIFE bundles! 🌐
• Wraps around the AssemblyScript Loader. The loader handles all the heavy-lifting of passing data into WebAssembly linear memory. 💪
• Wraps around imported JavaScript functions, and exported AssemblyScript functions of the AssemblyScript Wasm Module. This allows high-level data types to be passed directly to exported AssemblyScript functions! 🤯
• The library works at runtime, so no generated code that you have to maintain and make it play nicely in your environment. 🏃
• Maintains great performance (relative to generating the corresponding JavaScript code), by using Speculative Execution, and caching types passed between functions. 🤔
• Installable from package managers (npm), with a modern JavaScript API syntax. 📦
• The library is < 5KB (minified and gzip'd) and tree-shakeable! 🌲
• This library is currently (as of January, 2020) the wasm-bindgen in the Rust/Wasm ecosystem, for AssemblyScript. 😀

You can install as-bind in your project by running the following:

npm install --save as-bind

1. Compiling your Assemblyscript

To enable as-bind for your AssemblyScript Wasm modules, add the as-bind entrypoint when compiling your module:

asc ./node_modules/as-bind/lib/assembly/as-bind.ts your-entryfile.ts [...other cli options...]

For optional testing purposes , let's export an example function we can try in your-entryfile.ts:

export function myExportedFunctionThatTakesAString(value: string): string {
  return "AsBind: " + value;
}

2. In your Javascript

For browser JavaScript. We can do the following:

// If you are using a Javascript bundler, use the ESM bundle with import syntax
import { AsBind } from "as-bind";

// If you are not using a bundler add a <script> tag to your HTML
// Where the `src` points to the iife bundle (as-bind.iife.js), for example: https://unpkg.com/as-bind
// Then, INSTEAD of using the import syntax, do: `const { AsBind } = AsBindIIFE;`

const wasm = fetch("./path-to-my-wasm.wasm");

const asyncTask = async () => {
  const asBindInstance = await AsBind.instantiate(wasm);

  // You can now use your wasm / as-bind instance!
  const response = asBindInstance.exports.myExportedFunctionThatTakesAString(
    "Hello World!"
  );
  console.log(response); // AsBind: Hello World!
};
asyncTask();

For Node JavaScript, we would use the CommonJS bundle by do the following:

const { AsBind } = require("as-bind");
const fs = require("fs");

const wasm = fs.readFileSync("./path-to-my-wasm.wasm");

const asyncTask = async () => {
  const asBindInstance = await AsBind.instantiate(wasm);

  // You can now use your wasm / as-bind instance!
  const response = asBindInstance.exports.myExportedFunctionThatTakesAString(
    "Hello World!"
  );
  console.log(response); // AsBind: Hello World!
};
asyncTask();

Did the quick start not work for you, or you are noticing some weird behavior? Please see the FAQ and Common Issues

See the Quick Start

In this example, we will implement a console.log that we can call from AssemblyScript!

AssemblyScript

Inside of myWasmFileName.ts:

declare function consoleLog(message: string): void;

export function myExportedFunctionThatWillCallConsoleLog(): void {
  consoleLog("Hello from AS!");
}

JavaScript

import { AsBind } from "as-bind";

const wasm = fetch("./path-to-my-wasm.wasm");

const asyncTask = async () => {
  // Instantiate the wasm file, and pass in our importObject
  const asBindInstance = await AsBind.instantiate(wasm, {
    myWasmFileName: {
      consoleLog: message => {
        console.log(message);
      }
    }
  });

  // Should call consoleLog, and log: "Hello from AS!"
  asBindInstance.exports.myExportedFunctionThatWillCallConsoleLog();
};
asyncTask();

TL;DR: Currently Numbers, Strings, and Typed Arrays are supported. Returning a high-level data type from an imported JavaScript function, BigInt, and passing AssemblyScript Classes will be coming later.

Note: As discovered in #28, Array<NumberType> is NOT the same as TypedArray, and may not work for your use case. You want to use TypedArray where possible.

as-bind only supports AssemblyScript modules compiled with the --runtime full (default), and --runtime stub flags. These should be the only supported modes, because these runtime variants specify that you would like types / objects to be created externally as well as internally. Other runtime variants would mean that you DO NOT want anything externally created for your wasm module.

Please see the AssemblyScript Docs on runtime variants for more information.

The default exported ESM class of as-bind, also available as import { AsBind } from "as-bind" / const { AsBind } = require('as-bind').

The AsBind class is meant to vaugely act as the WebAssembly Object exposed to JavaScript environments.

AsBind.version: string

Value that is the current version of your imported AsBind.

AsBind.instantiate: (
  moduleOrBuffer: (
    WebAssembly.Module |
    BufferSource |
    Response |
    PromiseLike<WebAssembly.Module>
  ),
  imports?: WasmImports
) => Promise<AsBindInstance>`

This function is the equivalent to the AssemblyScript Loader instantiate function, which is similar to the WebAssembly.instantiateStreaming function. It essentially takes as its parameters:

• Any type of object that can be (resolved) and instantied into a WebAssembly instance. Which in our case would be an AsBindInstance.

• A WebAssembly importObject, which would have all of your imported functions that can be called from within your AssemblyScript module.

AsBind.instantiateSync: (
  moduleOrBuffer: (
    WebAssembly.Module |
    BufferSource
  ),
  imports?: WasmImports
) => AsBindInstance`

This is a synchronous version of AsBind.instantiate. This does not accept a promise-like as its module, and returns an AsBindInstance instead of a Promise that resolves an AsBindInstance. This is only reccomended for use in testing or development. Please see the Documentation sections for AsBind.instantiate for more information.

An AsBindInstance is vaugley similar to a WebAssembly instance.

Similar to to WebAssembly.Instance.prototype.exports, this is an object containing all of the exported fields from the WebAssembly module. However, exported functions are bound / wrapped in which they will handle passing the supported high-level data types to the exported AssemblyScript function.

Each exported function has the properties:

• shouldCacheTypes
  • If you would like to disable type caching (speculative execution) for a particular function, you can do: asBindInstance.exports.myFunction.shouldCacheTypes = false;. Or set to true, to re-enable type caching.
• unsafeReturnValue
  • By default, all values (in particular TypedArrays) will be copied out of Wasm Memory, instead of giving direct read/write access. If you would like to use a view of the returned memory, you can do: asBindInstance.exports.myFunction.unsafeReturnValue = true;. For More context, please see the AssemblyScript loader documentation on array views.
  • After settings this flag on a function, it will then return it's values wrapped in an object, like so: {ptr: /* The pointer or index in wasm memory the view is reffering to */, value: /* The returned value (TypedArray) that is backed directly by Wasm Memory */}

This is essentially the same as the WebAssembly.Instance.prototype.exports, this is an object containing all of the exported fields from the WebAssembly module. These are not bound / wrapped, so you can access the original exported functions.

Similar to to WebAssembly.instantiateStreaming() importObject, This is the original passed importObject on instantiation, after the importObject functions are bound / wrapped by as-bind.

Each wrapped importObject function has the property: shouldCacheTypes. If you would like to disable type caching (speculative execution) for a particular function, you can do: asBindInstance.importObject.myFunction.shouldCacheTypes = false;. Or set to true, to re-enable type caching.

Calling this method will (re-)enable type caching (speculative execution) for ALL exported functions on the AsBindInstance.

Calling this method will disable type caching (speculative execution) for ALL exported functions on the AsBindInstance.

Calling this method will (re-)enable unsafe return types for ALL exported functions on the AsBindInstance.

Calling this method will disable unsafe return types for ALL exported functions on the AsBindInstance.

Calling this method will (re-)enable type caching (speculative execution) for ALL importObject functions on the AsBindInstance.

Calling this method will disable type caching (speculative execution) for ALL importObject functions on the AsBindInstance.

This library was inspired by several chats I had with some awesome buddies of mine in the WebAssembly Community:

• Till Schneidereit and I had a chat about WasmBoy, and about how I had a really good experience writing the emulator, even though I had to do my own memory management. But they helped me realize, building something low level isn't that bad with manual memory management, but building something like a markdown parser would be very tedious since you have to manually write the string back and forth. Which then inspired this library, and its markdown parser demo.

• While I was building WasmByExample I wanted to start building the "High Level Data Structures" section. I then realized how much work it would be to maintain code for passing data between WebAssembly Linear memory would be for each data type, and how much work it would be to created each individual example. Then, my buddy Ashley Williams helped me realize, if your docs are becoming too complex, it may be a good idea to write a tool. That way you have less docs to write, and users will have an easier time using your stuff!

Thus, this library was made to help AssemblyScript/JavaScript users build awesome things! I also want to give a huge thanks to the AssemblyScript team and communitty for the help they provided me. I'm super appreciative of you all! 😄🎉

TL;DR This library should be fast, but depending on your project you may want some more careful consideration. 🤔

as-bind does all of its data passing at runtime. Meaning this will be slower than a code generated bindings generator, such as something like wasm-bindgen. This is because, as-bind needs to cycle through every supported type on every paremeter or return value for each function, whenever the function is called. However, this is mitigated due to the Speculative execution that the library implements.

Which in this case means, the library by default will assume the type of value being passed to, or returned by a function will not change. Thus, the library will only have to cycle through the params once, cache the types, and then for calls to the functions after this it would be as fast as a code generated solution (in theory). This speculative execution can be turned off as specified in the Reference API.

If your project is doing one-off processing using a high level data type, this project should have a very small impact on performance of your project. However, if you project is doing its processing in a very time constrained loop (such as a game running at 60fps), you may want to be more considerate when choosing this library. The speculative execution should greatly help in the amount of time to pass high level data types, but if your game is already not running as fast as you would like, you may want to avoid this library, or even not using high level data types, for passing memory to your WebAssembly module. However, the library also exposes all original exports under the AsBindInstance.unboundExports as covered in the Reference API, so you could, in theory, still access the non-bound exports without any of the performance overhead if you don't require any of the binding / wrapping that AsBind does for you.

Eventually for the most performant option, we would want to do some JavaScript code generation in the AssemblyScript compiler itself, as part of an as-bindgen project for the most performant data passing.

In the future, these types of high-level data passing tools will not be needed for WebAssembly toolchains, once the WebAssembly Inteface Types proposal lands, and this functionality is handled by the runtime / toolchain.

• The as-bind example is a Markdown Parser, in which as-bind takes in a string, passes it to a rough markdown parser / compiler written in AssemblyScript, and returns a string. (Live Demo), (Source Code)

• use-as-bind is a React hook for using as-bind with an as-bind enabled WASM source. It's goal is to provide a simple API for React users to add WASM to their apps. (Live Demo)

If you're project is using as-bind, and you would like to be featured here. Please open a README with links to your project, and if appropriate, explaining how as-bind is being used. 😊

I am calling my exports, but it is not returning the types that I am returning? It seems to be returning pointers?

This is probably because you are not adding the as-bind entry file. Please see the Quick Start on how to compile your AssemblyScript module with this entry file. If this still does not work, please take a look at the Supported Types to ensure what type you are trying to pass will work.

Didn't find a solution to your problem? Feel free to open an issue!

Contributions are definitely welcome! Feel free to open a PR for small fixes such as typos and things. Larger fixes, or new features should start out as an issue for discussion, in which then a PR should be made. 🥳

This project will also adhere to the AssemblyScript Code of Conduct.

MIT. 📝