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

@distrohelena/canton-explorer

v0.1.9

Published

Read-only operations explorer for Canton participant nodes and PQS-backed ledgers.

Readme

Canton Explorer

Read-only operations explorer for Canton participant nodes and PQS-backed ledgers.

This package runs a Nest backend and serves the built frontend from the same process.

Run From NPM

npx @distrohelena/canton-explorer --config ./config/nodes.local.json

By default the explorer binds to 0.0.0.0:4600.

CLI Options

canton-explorer --config ./config/nodes.local.json --port 4600 --host 0.0.0.0
  • --config points to the node config JSON file
  • --port overrides the HTTP port
  • --host overrides the bind host

You can also use environment variables:

PORT=4600
HOST=0.0.0.0
NODE_CONFIG_PATH=./config/nodes.local.json

Config

Create ./config/nodes.local.json in the directory where you run the command. Use config/nodes.example.json from this package as the starting point.

The explorer also expects the PQS PostgreSQL connection strings referenced by connectionUriEnv to be available in the environment.

For self-signed ES256 gRPC authentication, set the environment variable named by privateKeyEnv to the base64url encoding of the JSON private P-256 JWK. The auth configuration uses sub, aud, and privateKeyEnv; see config/nodes.example.json for the complete shape.

Local Debug DARs

The debugger can prefer local source-mapped DARs before falling back to the participant package service.

By default it scans:

./debug-dars

relative to the current working directory.

You can also set this explicitly in nodes.local.json:

{
  "debugger": {
    "localDarDirectory": "./debug-dars"
  }
}

Put sibling *-debug.dar files in that folder. The explorer indexes them by their main package id and uses them only for debugger source/artifact loading.

Generate Debug DARs

The published package includes the debug-DAR generation scripts. From an installed package, prepare debug DARs for every DAML package in a workspace:

npm --prefix ./node_modules/@distrohelena/canton-explorer \
  run dar:prepare-workspace -- \
  --workspace-root /path/to/daml-workspace \
  --output-dir /path/to/debug-dars

For one package, generate the source map and inject it into a sibling debug DAR:

npm --prefix ./node_modules/@distrohelena/canton-explorer \
  run dar:source-map -- \
  --input /path/to/package.dar \
  --workspace-root /path/to/daml-workspace

npm --prefix ./node_modules/@distrohelena/canton-explorer \
  run dar:debug -- \
  --input /path/to/package.dar \
  --source-map /path/to/package-source-map.json \
  --source-root /path/to/daml-project/daml=daml \
  --output /path/to/debug-dars/package-debug.dar

The generated debug DAR must retain the same compiled .dalf payloads as the original DAR. See the repository's docs/debug-dar.md for source-copy rules and source-map options.

Local Development

From the repo root:

npm install
npm run dev:backend
npm run dev:frontend

Backend: http://localhost:4600 Frontend: http://localhost:46000

Build The Publishable Package Locally

From the repo root:

npm run pack:dry-run

That builds the packaged frontend with /api as the API base, copies the frontend assets into the backend dist output, and performs an npm pack dry run for the publishable package.