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

@territory-kit/core

v1.2.0

Published

Core TerritoryKit zone engine, hierarchy, adjacency, and spatial queries.

Readme

@territory-kit/core

Core TerritoryKit engine APIs for hierarchical zones, spatial lookup, adjacency, bounds queries, and zoom-level transitions.

Installation

pnpm add @territory-kit/core @territory-kit/dataset

Basic Usage

import { readFile } from "node:fs/promises";
import { createTerritoryEngine } from "@territory-kit/core";
import { loadTerritoryDataset } from "@territory-kit/dataset";

const dataset = loadTerritoryDataset(input);
const adjacency = JSON.parse(await readFile("adjacency.json", "utf8"));
const engine = createTerritoryEngine({ dataset, adjacency });

const zoneId = engine.latLngToZone({ lat: 41.0, lng: 29.0 });
const sharedBorderNeighbors = engine.zoneNeighbors("tr:adm2:fatih", {
  types: ["shared-border"]
});

API Summary

  • createTerritoryEngine({ dataset, adjacency, levelStrategy }) builds the query engine.
  • latLngToZone(coordinate, options) locates the containing zone.
  • zoneNeighbors(zoneId, options) returns legacy neighbors and optional adjacency artifact neighbors.
  • getAdjacencyRelations(zoneId, options) returns typed artifact edges such as shared-border, point-touch, maritime, and logical.
  • getVisibleZones(query) and getViewportCacheKey(query) support viewport flows.
  • encodeTerritoryBinarySpatialIndex, decodeTerritoryBinarySpatialIndex, inspectTerritoryBinarySpatialIndex, and validateTerritoryBinarySpatialIndex provide the versioned .tksi binary spatial index contract with packed Flatbush tree data.
  • createTerritoryEngine({ dataset, spatialIndex }) accepts a prebuilt binary index and falls back to runtime Flatbush construction when no index is provided.
  • getSpatialIndexSummary() reports whether an engine is using flatbush or binary-flatbush lookup.
  • zoomToDefaultLevel and defaultZoomLevelStrategy provide default zoom mapping.
  • createTerritoryCountryDatasetDescriptor and loadTerritoryCountryDataset support thin resolver-driven country loader packages.

Registry client exports from the core root are deprecated compatibility exports. New code should import registry APIs from @territory-kit/registry; migration-only code can use @territory-kit/core/legacy-registry.

License

Apache-2.0