Package Exports

as-bind

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (as-bind) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

as-bind

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

Asbind Markdown Parser Demo Gif

Compatibility notes

Supported types (params and returns on exported functions FROM Assemblyscript):

Strings, TypedArrays

Supported types (params on import object functions. RETURNS NOT SUPPORTED):

Strings, TypedArrays

API Planning Notes

Maybe not asbind? Yes, as bind it matches up with what wasm bndgen says

Only supports the --runtime full, and --runtime stub flag. And should, because anything else would mean that you DO NOT want to create objects externally to your wasm module.

Simply need to wrap the docs from: https://docs.assemblyscript.org/details/runtime and we should be good to go!