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

@gamecrate/cli

v3.13.1

Published

Run a modded game in a container, with mods resolved from your local checkouts.

Readme

@gamecrate/cli

npm npm downloads MIT license Discord

Run a modded game in a Docker container. Describe your profiles, then launch it by name. Each profile gets its own settings, logs, and mod lists. Once a profile is set up, that is the whole command:

gamecrate run <profile>

Before you start

Right now, this only works on Linux. It may work in WSL, but it hasn't been tested. You'll also need Docker running, and a copy of the game.

gamecrate doctor checks all three and reports every problem together.

Set up your first profile

npm install -g @gamecrate/cli
gamecrate init

init installs the plugin for the game you want to use, and writes ~/.config/gamecrate/config.yml. It also offers to create a local .gamecrate.yml too, for a directory that holds a mod you are working on.

The global file holds the general configuration and defaults, and a project's .gamecrate.yml gives the specific configurations and profiles you use for a particular mod.

Where the game comes from is the one choice you have to make:

gamecrate read-only binds your install into the container at /game. The image supplies a few extra things around it: a virtual display, the graphics drivers, and the system libraries the engine links. Point gameFiles.host at the install directory, and the runtime image takes care of itself:

plugins: ['@gamecrate/rimworld']
games:
  rimworld:
    gameFiles:
      host: ~/.steam/steam/steamapps/common/RimWorld
    profiles:
      dev:
        mods: [concordlib.concord, yourname.yourmod] # more info on this coming later

With no image block (the runtime), gamecrate pulls ghcr.io/rimworks/gamecrate/runtime-base:1. That is about 160 MB, so this path needs no multi-gigabyte download and no registry of your own. Steam keeps the game itself up to date. You are welcome to create your own runtime image if you need to add more to it, or just want your own.

You can also build an image containing the entire game, based on the gamecrate runtime image. Run the commands below and gamecrate builds one for you:

gamecrate steam login
gamecrate steam build --game rimworld

The game lives inside that image, so drop gameFiles.host and set source: image instead:

plugins: ['@gamecrate/rimworld']
games:
  rimworld:
    gameFiles:
      source: image
    image:
      ref: rimworld:1.6
      acquire: pull
    profiles:
      dev:
        mods: [concordlib.concord, yourname.yourmod] # more info on this coming later

It tags the image with the game's own version, and with :latest

run pulls only when the image is missing, so a locally loaded image is left alone. gamecrate run dev --image <ref> does the same thing for one run without touching the config.

Configuration covers every key, and Game images covers the build.

Where a mod id comes from

A name like concordlib.concord is the mod's own package id, read out of its manifest. gamecrate builds an index of every mod it can see, then matches each name in mods against it. It looks in four places:

| Source | Holds | | --- | --- | | The Data directory in your install | The core game and its official DLC | | workshopRoot | Everything Steam downloaded for you | | scanRoots | Directories of your own, like a folder of checkouts | | The download directory | Anything gamecrate mods add pulled down for you |

The config here names none of the last three, so only the core game resolves. Add the ones you have:

    workshopRoot: ~/.steam/steam/steamapps/workshop/content/294100
    scanRoots:
      - path: ~/projects/mods
        maxDepth: 2

gamecrate mods <profile> lists what a profile resolves to and names anything it cannot find. To pin a mod gamecrate downloads itself, by workshop id or git URL, run gamecrate mods add. Mod sources covers every way to name one, and which copy wins when two match.

Launch it

gamecrate doctor              # every reason a launch could fail, reported together
gamecrate run dev --print-plan  # every path, mod and bind, without starting anything
gamecrate run dev

You can also run it detached, and have commands to manage the container after it is detached:

gamecrate run dev --detach
gamecrate ps                  # what is running, and how long it has been up
gamecrate logs dev -f         # follow this run's log
gamecrate stop dev            # free the profile

To point one mod at a working checkout and compile it first:

gamecrate run dev --use yourname.yourmod=~/projects/yourmod --build

You can use the gamecrate help command to find more info on the command-line tool itself. It also takes subcommands as arguments.

Where to go next

| Read this | When you want to | | --- | --- | | Configuration | Write the config file, load a plugin, define profiles, or set per-repository defaults | | Mod sources | Pin a mod to a directory, a git repository, or a workshop item gamecrate downloads, and learn which copy wins | | Running | Launch, run in the background, read the result, close a window, and clean up | | Game images | Build a launchable image from a game you own on Steam | | Reference | Every subcommand, flag, environment variable, and exit code | | Writing a plugin | Teach gamecrate a new game |

@gamecrate/rimworld is the RimWorld plugin, and the one complete example of the plugin contract.