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

vite-plugin-vue-bevy-wasm

v0.1.3

Published

Vite plugin to build bevy wasms

Readme

Vite Plugin Vue Rust Wasm

My first vite plugin, so take that into account before using.

Exports

  • virtual/vue-bevy/generated_wasms: List of generated crates

Notes

Wasm Size

There are 2 vite plugins I tried before starting my own.

I did get both working, rsw seems more complicated than was needed, the other didn't do as much, and neither used vite well, and both required manual steps, though both did work

  • Evan You interview - This interview was so helpful in understanding vite use of node modules resolution system, its dated but is making me rethink how important node modules are so vite can do more

Other references

Wasm-Pack

If you are new to rust and wasm, you kinda need to learn what each of the following do:

  • wasm-pack
  • wasm-bindgen
  • wasm-bindgen-cli
  • wasm-opt

For our use case, we are basically passing config options though 3 abstractions layers before anything useful happens because I don't care about publishing wasms on npm. Those options are:

--out-dir: where cargo build the file --out-name: what you told cargo build call it --profile: dev | release | profiling --target web

I found this after learning most of this the hard way Work With Wasm-bindgen for an overview. I disagree on author on one point though, I don't care about npm functionality because we can just tell vite where the files.

Setup

Requires wasm-bindgen-cli

cargo install -f wasm-bindgen-cli