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

@kuncat/avoidant

v0.3.1

Published

WebAssembly compilation target

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

aaksideaakside

Keywords

Readme

Avoidant

Developing

Prerequisites

WebAssembly compilation target

rustup target add wasm32-unknown-unknown

wasm-pack

cargo install wasm-pack

Nightly Rust toolchain (required for WebAssembly threads via wasm-bindgen-rayon)

rustup toolchain install nightly --component rust-src --target wasm32-unknown-unknown

On static hosting, ensure cross-origin isolation headers (for browser WebAssembly threads): Cross-Origin-Opener-Policy: same-origin and Cross-Origin-Embedder-Policy: require-corp

Running

Install dependencies with npm install then start a development server:

npm run dev

# or start the server and open the app in a new browser tab
npm run dev -- --open

Building

WASM

npm run build:wasm

App

npm run build

You can preview the production build with npm run preview.

Testing

WASM Headless Browser test

cd crates/game && wasm-pack test --headless --firefox

Multiplayer

The existing New Game menu offers Solo, Collaborative and Territory. All multiplayer modes require a Kuncat account and use the trusted Rust authority. Collaborative games share reveals and a team score; territory use their respective competitive rules. Invitations join through the same menu and login flow. Solo stays local and does not require an account. Iroh transport and peer host/join APIs have been removed.

See the implementation plan for rules, identity and architecture diagrams, and the server guide for deployment. The component's optional competitive configuration supplies the server URL and Kuncat account client for all multiplayer modes. Without configuration, multiplayer controls remain disabled. The sibling website configures shared OIDC; the sibling infra repository provisions identity, database and Workers.

npm ci
npm --prefix server ci
npm run dev:multiplayer -- --host

The local launcher supplies test accounts to the ordinary menu. Production builds exclude that adapter. Open the printed player URLs, choose New Game and a mode, then share the invitation link. No cloud provisioning is needed for local play.

cargo test -p avoidant --lib
cargo test -p avoidant-competitive
npm --prefix server test

The shared menu uses DaisyUI 5 with Tailwind 4. Consumers of the Svelte package must install daisyui and enable its Tailwind plugin (themes winter and night), as configured in src/app.css and the sibling games site's stylesheet.