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

unplugin-use-wasm

v2.0.1

Published

Support to "use wasm" directive to compile to WebAssembly

Readme

unplugin-use-wasm

npm version Checked with Biome NPM License

A Vite plugin that adds support for the "use wasm" directive in TypeScript files, enabling seamless integration and compilation of WebAssembly modules.

It uses the AssemblyScript compiler to compile TypeScript code into WebAssembly. AssemblyScript is a subset of TypeScript, it allows developers to write high-performance code that can be executed in a WebAssembly environment. So not every TypeScript code can be compiled to WebAssembly. For more info on that, check the AssemblyScript documentation.

Features

  • Multiple Bundler Support: Works seamlessly with Vite, Rollup, and Rolldown. Other bundlers may work but are not officially supported, since this is a unplugin.
  • Easy Integration: Simply add the plugin to your bundle configuration and use the "use wasm" directive in your TypeScript files.
  • Automatic Compilation: The plugin automatically compiles TypeScript files with the "use wasm" directive to WebAssembly using AssemblyScript.
  • Seamless Imports: Import and use WebAssembly modules in your application just like regular TypeScript modules.
  • Optimized Performance: WebAssembly modules are optimized for performance, making them ideal for computationally intensive tasks.
  • Vite First-Class Compatibility: Fully compatible with Vite, leveraging its fast build times and hot module replacement (HMR).
  • Customizable: Configure the AssemblyScript compiler flags and options to suit your project's needs.

Installation

npm install unplugin-use-wasm --save-dev

AssemblyScript types

This package also have the AssemblyScript portable types, so you do not get warnings when you try to use the types i32, f64, bool, etc.

In your tsconfig.json, add the following to the compilerOptions:

{
  "compilerOptions": {
    "typeRoots": ["./node_modules/unplugin-use-wasm/dist/types"],
    "types": ["assemblyscript"]
  }
}

Usage

First, add the plugin to your bundler configuration file, here I will use Vite for example (vite.config.ts or vite.config.js):

import { defineConfig } from "vite";
import useWasm from "unplugin-use-wasm/vite";

export default defineConfig({
  plugins: [
    useWasm({
      browser: true,
    }),
  ],
});

The import path can be changed to unplugin-use-wasm/rollup or unplugin-use-wasm/rolldown depending on the bundler you are using.

Then, you can use the "use wasm" directive in your TypeScript files to indicate that the file should be compiled to WebAssembly:

// sum.ts
"use wasm";

export function sum(a: i32, b: i32): i32 {
  return a + b;
}

You can then import and use the WebAssembly module in your application:

import { sum } from "./sum.ts";

const result = sum(1, 2);
console.log(result); // 3

Examples