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

@rust-js/create

v0.0.3

Published

`bun create @rust-js my-app`: a Vite and React app written in Rust. See docs/decisions/0105-create.md.

Readme

@rust-js/create

bun create @rust-js@latest my-app      # with Bun
npm create @rust-js@latest my-app      # with Node.js

makes my-app, a Vite and React app whose component is written in Rust (ADR 0105). It's the vite-react example's files, named for their directory, with rust-js's packages at this release's version, and it says the Rust release rust-js runs with, to install once. Either runs @rust-js/create, and it says the next commands of the one that ran it: bun install and bun run dev, or npm install and npm run dev.

Before you start

Three things, each installed once:

| What | Why | How | | --- | --- | --- | | Bun or Node.js | makes the app, installs it, and runs Vite: either one | Bun: curl -fsSL https://bun.sh/install \| bash. Node.js, ^20.19.0 or >=22.12.0, and its npm: nodejs.org's installer, or a version manager's | | rustup | installs and chooses Rust toolchains | curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs \| sh | | rust-js's Rust | the stable release rust-js is built with: rust-js runs with its rustc's own library, and checks the app for its wasm32-unknown-unknown target | rustup toolchain install 1.98.1 --profile minimal --target wasm32-unknown-unknown |

  • The Rust is about 500 MB: the minimal profile, rustc, Cargo and the standard library, for this machine and for wasm32-unknown-unknown. Not rustc-dev: that's for building rust-js, not for running it. rustup keeps it apart from the Rust you use, and making the app prints the command too.
  • Bun or Node.js, either. Node.js must be one Vite 8 runs on, ^20.19.0 or >=22.12.0, with Bun too if it's installed: bun run dev runs Vite on Node when there is one, and on Bun when there isn't.
  • macOS or Linux, on a machine @rust-js/native, the compiler, is built for.

Before a release is on npm

Give it a distribution, the directory bun run pack:distribution makes, and the app installs its packages. bunx and npm exec take the packed tarball by an absolute file: path, and run its command, create:

bun run pack:create target/create.tgz
bunx --package "file:$PWD/target/create.tgz" create my-app --local <distribution>
npm exec --package "file:$PWD/target/create.tgz" -- create my-app --local <distribution>

It never writes into a directory that isn't empty.