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 🙏

© 2026 – Pkg Stats / Ryan Hefner

c2wasm

v1.0.3

Published

compile c to wasm, the easy way

Downloads

1

Readme

c2wasm

I jumped through all the hoops for you, so you can convert c to wasm.

pieced together from various clues:

performance optimizations

The first output I generated was surprisingly bloated, (seemed to be inlining too much or something?, creating lots of i32 variables) also, wasn't faster than my carefully optimized javascript. but turns out clang has lots of optimization options - I ended up using -O3

imports and exports

wasm method, accessable from javascript

//make this weird macro
#define export __attribute__ ((visibility ("default")))

//then at least this looks reasonable.
export
int add (int a, int b) {
  return a + b
}

compile to wasm

cd examples/add
c2wasm add.c -o add.wasm

see ./example/add/add.js for how to call this from javascript

javascript method, accessable from wasm

#define export __attribute__ ((visibility ("default")))

//since this is undefined, it's treated as an import
void console_log (char* string, int length);

export
void hello () {
  char string[]="hello world";
  console_log(&string, sizeof(string));
}

compile the same as before, and again, see ./examples/hello/hello.js for how to call from javascript, and pass import in from javascript too.

future work

it's kinda lame to be downloading (and compiling) all these nasty c compilers to build a tiny bit of wasm. isn't the point of wasm to be an actually portable binary target? why can't we compile clang to wasm and then install clang.wasm from npm?

clang-in-browser does that. somebody should wrap that into a node module!

License

MIT