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

@jdmichaud/wasm-toolkit

v15.0.4

Published

Statically compiled clang binary and friends for WASM accessible via npx

Downloads

6

Readme

wasm-toolkit

Ensures your environment can compile C/C++ code to freestanding WASM. Either use the local clang installation or provides statically build binaries.

How to install

npm install @jdmichaud/wasm-toolkit

Build to wasm

cat > add.c
extern void *malloc(unsigned long size);

// add.c
int *add (int first, int second)
{
  int *i = malloc(sizeof (int));
  *i = first + second;
  return i;
}
<EOF>
npx clang --target=wasm32 \
  --no-standard-libraries \
  -Wl,--export-all -Wl,--no-entry -Wl,--allow-undefined \
  -o add.wasm add.c

Inspect a WASM file

npx wasm-objdump -x add.wasm

How to build

You will need:

  • cmake version 3 or above
npm run build

And hopefully npm pack will suffice to package the built tools.

Contribute

How to build on linux

You will need a C/C++ compiler (gcc 11 is fine) and cmake (at least version 3). To build clang, execute:

./make-clang-linux.sh

To build the WASM utilities:

./make-wabt-linux.sh

This should produce the clang/ldd and utilities statically linked binaries in the appropriate dist/ folder.

How to build on windows

You will need a C/C++ compiler (Visual Studio 2019 is fine) and cmake (at least version 3).

To build clang, execute:

./make-clang-win.sh

To build the WASM utilities:

./make-wabt-win.sh

Windows VM on linux

Useful documentation here: https://wiki.gentoo.org/wiki/QEMU/Windows_guest

Create a drive:

qemu-img create -f qcow2 win10.img 30G

Download a Windows ISO from microsoft website.

Download the windows drivers ISO image:

curl -sOL https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win.iso

Start the VM (replace the ISO name accordingly):

qemu-system-x86_64 -enable-kvm \
  -cpu host \
  -drive file=win10.img,if=virtio \
  -net nic,model=rtl8139 \
  -net user,hostname=windowsvm \
  -m 16G \
  -monitor stdio \
  -name "Windows" \
  -boot d \
  -drive file=WindowsISO.iso,media=cdrom \
  -drive file=virtio-win-0.X.XXX.iso,media=cdrom

You might want to install windows without the -nic option first to avoid creating an online account and enable the option on the first boot.

Once virtdio drivers are install, you can add the options:

-vga virtio
-smp cores=$(nproc)

On windows, you will need build tools to be installed. You can find them there.

Additionally, you will need cmake and python (at least 3.9).