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 🙏

© 2025 – Pkg Stats / Ryan Hefner

wcpp

v1.2.0

Published

C++ for JavaScript

Readme

WCPP

A node module to make writing C/C++ in JavaScript not painful.

Using the power of WebAssebly, wcpp projects run both in node and on the web.

npm i -g wcpp

Installing Emscripten

WCPP comes with an Emscripten installer and will automatically source environment variables upon compile.

$ wcpp-install

A C++ File

// addTwo.cpp

export int addTwo(int a, int b) {
  return a + b;
}

We need export to tell our compiler to make this function available to JavaScript.

To compile all of our C/C++ files to wasm, we enter our project root and run:

$ wcpp

The first time running this command will be a bit slow.

You should see a list of C/C++ files that have been compiled.

Our JavaScript

All we have to do now is require our C++ file the same way we would require a JS file.

require('wcpp')

const ourModule = require('./addTwo.cpp')

console.log(ourModule.addTwo(2, 3))

If you want to both use wcpp in the web and inculde a lare C++ file, you'll need to use it asynchronously.

We could put this in an anonymous async function:

;(async () => {
  // Require our module
  const addTwo = await require('wcpp')('./addTwo.cpp')

  console.log(addTwo(2, 3))
})()

Or use it as a promise:

require('wcpp')('./addTwo.cpp').then(addTwo => {
  console.log(addTwo(2, 3))
})

Use Functions as Modules

We can make our function into a module by naming the function module

// C++

export int module(int a, int b) {
  return a + b;
}

export int timesTwo(int a, int b) { // We can still make other functions
  return a * b;
}
// JavaScript

require('wcpp')

const addTwo = await require('./addTwo.cpp')

console.log(addTwo(2, 3))
console.log(addTwo.timesTwo(2, 3)) // Our other function