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

jwt-compact-wasm

v0.0.19

Published

Usability of `jwt-compact` in WASM

Downloads

61

Readme

Testing jwt-compact Crate in WASM

This simple crate tests that jwt-compact builds and can be used in WASM.

Note that chrono and getrandom crates need to be configured in Cargo.toml in order to work with the WASM target:

[dependencies]
chrono = { version = "0.4.22", features = ["wasmbind"] }
getrandom = { version = "0.2", features = ["js"] }

Usage

  1. Install WASM target for Rust via rustup: rustup target add wasm32-unknown-unknown.
  2. Install wasm-pack.
  3. Install Node.
  4. Switch to the directory with this README and run wasm-pack build --target bundler.
  5. Run the testing script: node test.js.

:::note

If you are using wasm-bindgen without workers-rs / worker-build, then you will need to patch the JavaScript that it emits. This is because when you import a wasm file in Workers, you get a WebAssembly.Module instead of a WebAssembly.Instance for performance and security reasons.

To patch the JavaScript that wasm-bindgen emits:

  1. Run wasm-pack build --target bundler as you normally would.
  2. Patch the JavaScript file that it produces (the following code block assumes the file is called mywasmlib.js):
import * as imports from "./mywasmlib_bg.js";

// switch between both syntax for node and for workerd
import wkmod from "./mywasmlib_bg.wasm";
import * as nodemod from "./mywasmlib_bg.wasm";
if (typeof process !== "undefined" && process.release.name === "node") {
	imports.__wbg_set_wasm(nodemod);
} else {
	const instance = new WebAssembly.Instance(wkmod, {
		"./mywasmlib_bg.js": imports,
	});
	imports.__wbg_set_wasm(instance.exports);
}

export * from "./mywasmlib_bg.js";
  1. In your Worker entrypoint, import the function and use it directly:
import { myFunction } from "path/to/mylib.js";

:::

src: https://github.com/cloudflare/cloudflare-docs/blob/95aacf2eee782e3a89525b0f0855f02959367536/src/content/docs/workers/languages/rust/index.mdx?plain=1#L154