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

@carbonenginejs/tools-core

v0.8.0

Published

Node toolchain for CarbonEngineJS acquisition, generated libraries, caches, graph output, and optional HTTP service hosting.

Readme

@carbonenginejs/tools-core

Node.js tooling for exact-build acquisition, shared caches, deterministic libraries, and local services.

Use tools-core when a build or application needs Node filesystems, persistent caches, credentials, servers, command-line orchestration, or generated artifacts. Browser clients belong in @carbonenginejs/runtime/tools; runtime code never imports this package.

Install

npm install @carbonenginejs/tools-core

Node.js 18 or newer is required.

Quick start

import { CjsToolIndex } from "@carbonenginejs/tools-core/index";

const source = await new CjsToolIndex().Open({
    target: "eve",
    build: "latest",
});

const resolved = source.Resolve(
    "res:/dx9/model/spaceobjectfactory/data.red",
);

console.log(resolved);

Friendly build names resolve once; subsequent reads retain the exact target and numeric build. Provider and game are provenance metadata. Indexed payloads are checked against declared size and MD5 before they are returned or cached.

What it owns

  • app/resource index acquisition and the shared exact-build cache;
  • profile-driven exact-build cache preparation before tools or services start;
  • prepared SDE databases, composed icon resource paths, and Node-side orchestration/publication of deterministic audio, character, SKIN, SKINR, weapon, and shader outputs;
  • self-contained SOF bundles for consumers without Carbon or a DDS decoder;
  • schema scanning and class-emission tooling;
  • optional loopback HTTP and filesystem-watch services.

Each area is independently importable through a documented package subpath. The runtime audio and character layers own their raw-resource build algorithms; tools-core supplies target-selected exact-build bytes and persists their GetValues() output. The character subpath also gathers optional prepared model-shaped JSON records and materializes sparse part-source authoring into complete effective metadata and exact resource-candidate inventories, while @carbonenginejs/runtime/character owns the combined schema-v10 model and hydration contract. Decoded character definitions are retained losslessly; typed catalogs are additive indexes.

Documentation

Development

npm run check

The baseline check is offline and uses synthetic fixtures or injected network implementations. Acquired data, caches, reports, SQLite files, credentials, and private work material must not be committed or published.

License

MIT. See LICENSE and NOTICE. CarbonEngine, Fenris Creations (CCP Games), Twitch, and Kick names and API terms are used solely for interoperability and provenance. This project is not affiliated with or endorsed by those organizations.