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

@here.build/lexical-namer

v0.9.0

Published

Lexical-scope-aware name assignment. Takes a scope tree of entities with prioritized name candidates, returns a non-colliding assignment that respects parent-chain visibility, sibling independence, and symmetric tie resolution.

Readme

@here.build/lexical-namer

Priority-based name assignment, flat and lexically-scoped. One resolution algorithm exposed through two public APIs over the same core:

assignNames          : flat pool, one resolution pass
resolveLexicalNames  : tree of pools, one pass per scope,
                       with parent-chain reservations folded in

assignNames is a thin adapter over the scope resolver — it builds a single childless root scope and delegates, so there is exactly ONE algorithm to reason about. Use it for CSS classes or any single-namespace pool. Use resolveLexicalNames for JS identifiers and other lexically-scoped namespaces.

Concepts

  • Scope tree — input is a ScopeSpec<E> whose children recursively form the tree. Each scope has its own reservations and entities.
  • Parent-chain visibility — a name claimed in scope S is visible (reserved) in any descendant of S, but NOT in siblings.
  • Sibling independence — two siblings can independently assign the same name; their resolutions don't see each other.
  • Priority ladders — each entity offers a Record<priority, candidate> ladder; higher priority wins, collisions fall to the next rung.
  • Per-scope tie semanticsonTie: "burn" | "free" | "postfix" controls what happens to a bare name contested at one tier: burn it for lower tiers, leave it claimable, or postfix all tied entities immediately.

API

import { resolveLexicalNames, type ScopeSpec } from "@here.build/lexical-namer";

const root: ScopeSpec<string> = {
  id: "root",
  entities: [
    { key: "a", candidates: { 100: "open", 80: "openState" } },
    { key: "b", candidates: { 100: "open", 80: "openFlag" } },
  ],
};

const result = resolveLexicalNames(root, {
  postfixFor: (key) => key, // must be injective across the entity set
  resolveTie: (name, postfix) => `${name}_${postfix}`, // JS-friendly
  onTie: "burn",
});

result.assignments.get("a"); // → assigned name (e.g. "openState")

For a single flat namespace (CSS classes, etc.), reach for assignNames instead — same candidate ladders, one pool, onTie: "postfix" by default.

See src/index.ts for the full type surface and src/__tests__/resolver.test.ts for the contract.

Status

Shipped and tested. The resolver (resolveLexicalNames plus the assignNames adapter) is fully implemented; 170 tests across 5 files pass (pnpm -F @here.build/lexical-namer test).

License

FSL-1.1-MIT — Functional Source License 1.1, MIT Future License. Each version converts to MIT two years after its release date. Until conversion, the license permits everything except Competing Use (making the Software available in a commercial product or service that substitutes for the Software or offers substantially similar functionality). Internal use, non-commercial education and research, and professional services built on top of the Software are always permitted.

For licensing questions, exemptions, or clarifications: [email protected]