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

nexmap4

v1.2.2

Published

Standalone nexMap4 package built from source-owned map and runtime data.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Maintainers

khaseemkhaseem

Keywords

achaeanexusmudnexmap

Readme

nexMap4

nexMap4 is a standalone Nexus package with a single-package build target.

Pathing is designed around one computed route and two execution modes: a hybrid server-assisted mode that uses Achaea's path track where eligible, and a pure client-stepped mode that preserves room-by-room automation opportunities inside nexMap4. The active mode is a user-configurable nexMap4 setting.

Implementation uses the source-owned data checked into src/assets and src/nexmap/data. Sibling legacy repositories and deleted rebuild artifacts are not implementation inputs.

The production Nexus artifact is one minified JavaScript bundle, dist/nexmap4.min.js, published from this repository and imported into the Nexus client. Localhost development now runs through a standard Vite app shell that mounts the same nexMap4 tab container used by the production bootstrap. nexMap4 is not a workspace or monorepo. It follows the same single-root solution pattern used by nexSys4 and nexGui4: one package, one root src/, one root tests/, and one root Vite/Vitest toolchain.

Layout

  • src/index.js: root public API surface for internal imports and tests
  • src/main.jsx: localhost React/Vite entry that mounts the playground shell
  • src/App.jsx: localhost React shell that renders the production nexMap4 tab through the Nexus-style FlexLayout override
  • src/nexmap/bootstrap/bootstrapNexusEntry.js: single Nexus bundle entry used by Vite build
  • src/nexmap/bootstrap/bootstrapPlayground.js: mock-host playground bootstrap for localhost testing
  • src/nexmap/*: nexMap4 runtime modules under one coherent source tree
  • tests/hostEventHarness.js: synthetic host-event fixture loader and replay harness
  • tests/fixtures/host-events/: synthetic event fixtures used before deferred runtime traces exist
  • tests/: root test tree for unit, integration, and perf suites

Runtime behavior now lives in the source tree and is covered by the root test suite.

Design Docs

Commands

npm run dev
npm run build
npm run build:watch
npm test
npm run lint