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

@acastellon/ws-dns

v1.1.0

Published

WS DNS system (Ad-hoc Discovery WS system)

Readme

@acastellon/ws-dns

WS DNS system ( Ad-hoc Discovery WS system) - server side for service registration/discovery.

This module was incomplete/minimal in the original repo. It is the server counterpart to the @acastellon/dns-client module.

Intended API / Endpoints (implement these)

Typical REST/WS endpoints a full implementation should expose (versioned):

  • GET /:version/ping → 200/201 if healthy
  • GET /:version/get/:service_id → returns { service: { PROTOCOL, IP_OR_CNAME, PORT, METHOD } } or error
  • POST /:version/set/:service_id with body { PROTOCOL, PORT, METHOD } → registers the service address

Example server skeleton (what you would implement):

const express = require('express');
const app = express();

app.use(express.json());

const services = {}; // or use a real store

app.get('/:version/ping', (req, res) => res.sendStatus(200));

app.get('/:version/get/:service_id', (req, res) => {
  const svc = services[req.params.service_id];
  if (svc) res.json({ service: svc });
  else res.status(404).json({ error: 'not found' });
});

app.post('/:version/set/:service_id', (req, res) => {
  services[req.params.service_id] = req.body;
  res.sendStatus(201);
});

app.listen(7777, () => console.log('WS DNS server stub running'));

Install

npm install @acastellon/ws-dns

Current stub

The index.js exports a factory that returns a minimal object with start, register, get. Replace with real Express + storage.

License

MIT