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

webassembly-types

v1.0.0

Published

Better types for interacting with WebAssembly

Downloads

8

Readme

webassembly-types

Better types for interacting with WebAssembly

Install

Using npm:

npm install --save webassembly-types

or using yarn:

yarn add webassembly-types

Usage

API:

const types = require("webassembly-types");

types.i32(12);
types.i64(12);
const a = types.i64(12n);

// call an export
instance.exports.fn(a);

Why

stricter range checks

To be consistent with JavaScript, out-of-range numbers passed in WebAssembly do silently overflow. This can be pretty error-prone, as shown by the following example:

(module
  (memory 1)
  (func (export "load") (param i32) (result i32)
    (get_local 0)
    (i32.load)
  )
)
instance.exports.load(4294967296);

Will load at offset 0 because it overflowed at the Wasm boundary.

Using the i32 from this lib will make it throw instead.

simpler i64

In JavaScript BigInt are not convertible to Number, this can be annoying when trying to keep your JavaScript<>Wasm code generic.

For instance, the previous example could be compiled for both 32-bit and 64-bit address space. In 64-bit mode is would look like the following:

(module
  (memory 1)
  (func (export "load") (param i64) (result i64)
    (get_local 0)
    (i64.load)
  )
)

The call here, wouldn't work anymore (it will throw instead):

instance.exports.load(4294967296);

Using the lib:

instance.exports.load(i64(4294967296));