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

@kingdomsconnected/types

v1.8.1

Published

TypeScript declarations for the Kingdoms Connected scripting API, one entry per side: @kingdomsconnected/types/server and @kingdomsconnected/types/client

Readme

@kingdomsconnected/types

TypeScript declarations for the Kingdoms Connected scripting API, generated from the runtime's own bindings and published with every release. The package version is the release version.

pnpm add -D @kingdomsconnected/types

A resource runs in the server's Node.js isolate or in a client's sandboxed V8 one, and the two declare different globals -- the server's Player has the connection verbs, the client's does not -- so they are two TypeScript programs, each naming its side in types:

// tsconfig.json (server half)
{
  "compilerOptions": {
    "lib": ["ES2022"],
    "types": ["@kingdomsconnected/types/server"]
  }
}
// src/client/tsconfig.json (client half)
{
  "compilerOptions": {
    "lib": ["ES2022"],
    "types": ["@kingdomsconnected/types/client"]
  }
}

Everything is declared as a global, as the runtime installs it: Events, console, the timers, Player, Vector3 and the rest need no import. The DOM library would declare a second setTimeout and console, so leave it out of lib.

Install the version matching the server you deploy to; a newer package may declare bindings an older server does not have.