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

@maxijonson/rust-maps-api

v0.0.10

Published

Unofficial Node.js clients for the Rust Maps API.

Readme

⚠️ Unstable - Use at your own risk

This project relies on Rust Maps' OpenAPI spec to automatically generate clients. However, as of October 2025, the spec currently has a lot of issues, making the generated clients unreliable. Use at your own risk.

Examples of issues include the following. Note that these are just examples from my own usage in projects, and there may be many more.

  • MonumentTypes and BiomeTypes are typed as integer instead of string. A patch has been configured in this project to fix this.
  • Search.searchRaw request schema has a lot of incorrectly typed fields, making it practically unusable. largeMonuments is typed as MonumentTypes, though not all MonumentTypes are valid values for this field. This was also (partly) patched by examining how requests are made on the Rust Maps website.

Installation

npm install @maxijonson/rust-maps-api

Usage

Import the client classes you need from the package. Currently, you can use one of the following clients:

  • Search
  • Misc
  • Maps
  • SubscriptionRequired
  • MapsUpload
// 1. Import the needed client classes
import { Search, Misc, Maps, SubscriptionRequired, MapsUpload } from "@maxijonson/rust-maps-api";

// 2. Use the clients
// Example: Search for maps with a size of exactly 4000
const { data, error } = await Search.searchRaw({
  query: {
    page: 0,
    customMaps: false,
  },
  body: {
    searchQuery: {
      size: {
        min: 4000,
        max: 4000,
      },
    },
  },
  auth: process.env.RUST_MAPS_API_KEY,
});
console.log(data, error);

Documentation

See Rust Maps API documentation.

Development

Clone the repository and install dependencies:

git clone https://github.com/maxijonson/rust-maps-api.git
cd rust-maps-api
npm install

To generate the clients, run:

npm run generate

(Only for maintainers) Automatically update the clients and publish them to NPM with one command:

# This bumps the version, builds the project, pushes to git and publishes to NPM
npm version patch # or minor or major

Contributing

Apart from configuration, everything is automatically generated from the OpenAPI spec. No manual changes are made to the generated code. If you find the generated clients are outdated, you can let me know and I'll run the generation script again and publish them to NPM. This project doesn't do anything fancy that you wouldn't be able to do yourself with Hey API.

If you do contribute however, please don't waste your time updating the generated code, as it will be overwritten when I publish your changes to NPM. If something is wrong in the generated code, please try to fix it via the openapi-ts.config.ts configuration file, not in the generated code.

Though I prefer you not include changes to generated code in your pull requests, you may still do. However, just know that if your PR is merged, any changes to generated code will automatically be overwritten the next time I publish to NPM.