npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

wat2js

v2.1.1

Published

Compile WebAssembly .wat files to a common js module

Downloads

2,395

Readme

wat2js

Compile WebAssembly .wat files to a common js module

npm install -g wat2js

See https://github.com/WebAssembly/wabt for more WebAssembly goodies.

Currently requires the wat2wasm program to be installed globally. If you don't have that already you can get that by installing the webassembly binary toolkit by using this little helper

Usage

First make a basic WebAssembly .wat file

;; example.wat
(module
  ;; var result = add(a, b)
  (func (export "add") (param $a i32) (param $b i32) (result i32)
    ;; return a + b
    (i32.add
      (get_local $a)
      (get_local $b)
    )
  )
)

Then compile it to WebAssembly and wrap in a common js loader by doing

wat2js example.wat -o example.js

To run the WebAssembly simply do:

var example = require('./example.js')() // load the wasm
if (!example) throw new Error('WebAssembly not supported by your runtime')

var result = example.exports.add(1, 2)
console.log('1 + 2 = ' + result)

To keep recompiling the .wat file when it changes pass the --watch option as well

wat2js example.wat -o example.js --watch # recompile when example.wat changes

You can also pass arguments to wat2wasm:

wat2js example.wat -o example.js --watch -- --debug-names # add debug names section

API

var mod = require('./compiled-wat.js')([options])

Loads your WebAssembly module. If WebAssembly is not supported by the runtime, null is returned.

Options include:

{
  imports: {...} // import objected forwared to WASM,
  async: true // force async loading.
}

Note that if your WASM is larger than 4kb, some browsers might force async loading.

mod looks like this

{
  exports: {...}, // exports WASM functions
  memory: Uint8Array, // exports.memory wrapped in a uint8array (if exported)
  buffer: Uint8Array, // the WASM module as a buffer
  onload: onload(cb), // function you can call to wait for async loading
  realloc: realloc(bytes) // reallocate the memory buffer to a new size
}

In case of async loading exports and memory will be null until the module has been loaded.

License

MIT