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 🙏

© 2024 – Pkg Stats / Ryan Hefner

minestat-es

v1.1.5

Published

Promise-based Minecraft server status

Downloads

432

Readme

minestat-es

Package Version Code Coverage

features

  • Written in TypeScript
  • Less than 5kB of code
  • No runtime dependencies
  • Supports ESM and CommonJS
  • Comprehensive unit tests

requirements

  • Node 16+

usage

by address/port

To query a Minecraft server using an IP/hostname and a port, use:

fetchServerInfo({
  address: '1.2.3.4',
  port: 25565,
  timeout: 1000
});

by hostname

To perform an SRV record lookup and query a Minecraft server using only a hostname, use:

fetchServerInfo({
  hostname: 'example.com',
  timeout: 1000
});

Regardless of which way it was invoked, fetchServerInfo returns a promise which will resolve with an object containing the following properties:

| Key | Type | Description | | ------ | --------- | ----------------------------------- | | online | boolean | Whether the server is online or not |

If the server is offline, the object will also contain the properties:

| Key | Type | Description | | ----- | ------- | ----------------------------------------------------- | | error | Error | A communications or validation error, if one occurred |

If the server is online, the object will also contain the following properties:

| Key | Type | Description | | ---------- | -------- | ------------------------------------------------- | | version | string | The server's version string | | motd | string | The server's Message of the Day | | players | number | The number of players on the server | | maxPlayers | number | The maximum number of players the server supports |

fetchServerInfo rejects if an error occurs during SRV record resolution.

example

import { fetchServerInfo } from 'minestat-es';

(async () => {
  try {
    // query by hostname (SRV lookup)
    const { online, error, players } = await fetchServerInfo({
      hostname: 'mc.example.com'
    });

    // OR

    // query by address/port
    const { online, error, players } = await fetchServerInfo({
      address: 'example.com', // could also be an IP address
      port: 25565
    });

    // interpret the results
    console.log(`Server is ${online ? 'Online' : 'Offline'}`);
    if (online) {
      console.log(`There are ${players} player(s) online.`);
    } else if (error) {
      // either the SRV record failed to resolve, a socket error occurred,
      // or the response from the server was invalid
      console.error(error);
    }
  } catch (error) {
    // an unexpected error occurred
    console.error(error);
  }
})();