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

vite-plugin-nimbling

v0.1.1

Published

Vite plugin for Nim → WebAssembly via nimbling

Readme

vite-plugin-nimbling

Vite plugin for nimbling — import .nim files directly in your Vite projects.

Installation

npm install --save-dev vite-plugin-nimbling

Make sure you also have the nimbling CLI installed (via nimble):

nimble install nimbling
# or use the local CLI:
nimbling --help

Usage

// vite.config.js
import { defineConfig } from 'vite';
import nimbling from 'vite-plugin-nimbling';

export default defineConfig({
  plugins: [
    nimbling({
      // Options:
      target: 'web',        // 'web' | 'bundler' | 'nodejs' | 'deno'
      cliPath: 'nimbling',  // path to nimbling CLI binary
      cacheDir: '.nimbling-cache',
      verbose: false,
    })
  ]
});

Then in your app:

import { greet, add } from './counter.nim';

async function main() {
  await greet();   // nimbling handles init() automatically
  console.log(add(2, 3));
}
main();

How It Works

  1. Intercept .nim imports — the plugin resolves *.nim files before Vite processes them.
  2. Compile to WASM — runs nim c --cpu:wasm32 + clang --target=wasm32 to produce .wasm.
  3. Generate JS glue — runs nimbling CLI on the .wasm to emit the JavaScript bindings.
  4. Emit as Vite asset — copies _bg.wasm to dist/_nimbling/ during build.

If you already have a pre-built .wasm next to your .nim, it will be used directly.

HMR (Hot Module Replacement)

Editing a .nim file in dev mode (vite dev) triggers:

  1. Automatic recompilation
  2. Full page reload — WASM modules cannot be safely hot-swapped, so a full reload is issued. This ensures the new .wasm is picked up cleanly.

Configuration Options

| Option | Type | Default | Description | |-------------|-----------|---------------------|----------------------------------------------| | target | string | 'web' | JS target: web, bundler, nodejs, deno | | cliPath | string | auto-detect | Path to nimbling CLI binary | | cacheDir | string | .nimbling-cache | Directory for intermediate files | | nimOptions| string | '' | Extra flags passed to nim c | | verbose | boolean | false | Log compilation commands |

Requirements

  • Vite 4.x / 5.x / 6.x
  • Nim 2.x
  • nimbling CLI (install via nimble install nimbling)
  • clang with WASM target support

License

MIT