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

@srvquery/protocol-fivem

v0.0.1-next.1

Published

Readme

@srvquery/protocol-fivem

npm Version npm Weekly Downloads

Query FiveM and RedM (FXServer) game servers.

Installation

pnpm add @srvquery/core @srvquery/protocol-fivem

Usage

import { createFiveMProtocol } from "@srvquery/protocol-fivem";

const fivem = createFiveMProtocol({
  host: "127.0.0.1",
  port: 30120,
});

const info = await fivem.query({ opcode: "INFO" });
const players = await fivem.query({ opcode: "PLAYERS" });
const dynamic = await fivem.query({ opcode: "DYNAMIC" });

console.log(`${dynamic.hostname}: ${dynamic.clients}/${dynamic.sv_maxclients}`);
console.log({ info, players });

Locating a server by Cfx.re id

Servers can also be located by their Cfx.re server id (the short code used in join links such as https://cfx.re/join/<id>) instead of a host/port pair. The id is resolved to the server's advertised connect endpoint on first use and cached for the lifetime of the returned client.

import { createFiveMProtocol } from "@srvquery/protocol-fivem";

const fivem = createFiveMProtocol({ id: "abcdef" });

const info = await fivem.query({ opcode: "INFO" });

Query types

| Opcode | Endpoint | Description | | --------- | --------------- | ----------------------------------------------------------------------------------------- | | INFO | /info.json | Server version, icon, resources and vars convars | | PLAYERS | /players.json | Connected players: id, name, ping, identifiers | | DYNAMIC | /dynamic.json | Lightweight, server-browser-oriented summary (hostname, gametype, mapname, client counts) |

Stripping formatting codes

FiveM/RedM allows ^-prefixed color and formatting codes (e.g. ^1 for red) in strings such as hostnames and player names. Pass stripFormattingCodes: true to recursively strip them from every string in the response:

const info = await fivem.query({ opcode: "INFO", stripFormattingCodes: true });

Reference: Chat Formatting // Colors, Bold, Underline