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

@ninjutsu-build/swc

v0.1.0

Published

An SWC plugin for ninjutsu-build

Downloads

54

Readme

swc - Ninjutsu Build

A package to create a ninjutsu-build rule for transpiling TypeScript and JavaScript files using SWC.

Unlike @ninjutsu-build/tsc, this plugin only transpiles and does not perform type checking or generate type declarations. This makes it faster and well-suited for use alongside @ninjutsu-build/tsc (for type declarations) so that typechecking and test execution can run in parallel.

Prerequisites

This project requires NodeJS (version 22 or later), npm, and @swc/cli.

Installation

Most likely you require @ninjutsu-build/swc, @ninjutsu-build/core, and @swc/cli as devDependency packages, which can be achieved by running the following npm command:

$ npm install @ninjutsu-build/core @ninjutsu-build/swc @swc/cli --save-dev

Basic Example

Given the following TypeScript file,

// src/add.ts
export function add(a: number, b: number): number {
  return a + b;
}

We can build a build.ninja file that will transpile src/add.ts to dist/add.js,

import { NinjaBuilder } from "@ninjutsu-build/core";
import { makeSWCRule } from "@ninjutsu-build/swc";
import { writeFileSync } from "node:fs";

// Create a `NinjaBuilder`
const ninja = new NinjaBuilder({
  ninja_required_version: "1.1",
  builddir: ".builddir",
});

// Create the `swc` rule, passing SWC arguments that apply to all build edges
const swc = makeSWCRule(ninja, {
  args: ["-C", "jsc.target=es2018", "-C", "module.type=commonjs"],
});

swc({
  in: "src/add.ts",
  out: "dist/add.js",
});

writeFileSync("build.ninja", ninja.output);

Run this script with node --experimental-strip-types configure.ts (or npx tsx configure.ts etc.) and then run ninja!

Overriding args per build edge

SWC arguments set at the rule level apply to every build edge, but can be overridden for individual build edges by passing args directly,

const swc = makeSWCRule(ninja, {
  args: ["-C", "jsc.target=es2018", "-C", "module.type=commonjs"],
});

// This edge overrides the module type to ES modules
swc({
  in: "src/index.mts",
  out: "dist/index.mjs",
  args: ["-C", "jsc.target=es2018", "-C", "module.type=es6"],
});