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

@phyloviz/phylo-lens

v0.2.1

Published

Headless, scalable phylogenetic tree visualization client. Server-side level-of-detail with a Sigma.js renderer, consumable as a library by host apps such as PHYLOViZ.

Readme

PhyloLens browser library

@phyloviz/phylo-lens is the public browser package for embedding a PhyloLens visualization in a host application.

The package owns the complete client lifecycle:

  • service compatibility validation;
  • graph preparation and status polling;
  • viewport synchronization;
  • semantic-zoom tier selection;
  • Sigma/Graphology renderer lifecycle;
  • metadata-driven visual mappings;
  • cluster expansion and collapse.

The host application supplies a DOM container, a PhyloLens API service base URL, and input content. HTTP DTOs, job identifiers, layout versions, renderer factories, and viewport controllers are internal implementation details.

Installation

npm install @phyloviz/phylo-lens

The package is ESM-only and includes TypeScript declarations. Sigma, Graphology, and the renderer plug-ins used by the default implementation are installed as package dependencies.

Basic integration

import { createPhyloLensView } from "@phyloviz/phylo-lens";

const container = document.getElementById("graph-root");
if (!(container instanceof HTMLElement)) {
  throw new Error("Missing graph container.");
}

const view = createPhyloLensView({
  container,
  apiUrl: "/phylo-lens",
});

await view.load({
  content: "(A:1,(B:2,C:4)N:3)R;",
  name: "example-tree",
  sourceFormat: "newick",
});

view.dispose();

load() resolves only after:

  1. the service reports a compatible API contract;
  2. preparation completes successfully (including any expensive global sfdp layout; the default wait is unlimited);
  3. the first viewport response is received;
  4. the first graph snapshot is applied to the renderer.

A newer load() supersedes an older in-flight load. dispose() invalidates pending loads and releases renderer event handlers and resources.

exportPng() returns a reusable Blob for the current visible view. It keeps the current camera, semantic-zoom materialization, and visible Sigma canvas layers; it does not trigger a browser download or change the view state. SVG is not currently exposed because faithfully reproducing Sigma's WebGL/custom-program rendering as vector geometry requires a separate vector renderer.

Public package surface

The package root exports:

createPhyloLensView
PhyloLensView
PhyloLensViewOptions
PhyloLensLoadOptions
MetadataField
SourceFormat
Viewport
VisualMappingOptions
PhyloLensServiceUnavailableError
PhyloLensServiceProtocolError
IncompatiblePhyloLensServiceError
SUPPORTED_PHYLO_LENS_API_VERSION

Transport clients, workbench classes, renderer adapters, Graphology types, and HTTP response DTOs are intentionally not exported.

createPhyloLensView

function createPhyloLensView(options: PhyloLensViewOptions): PhyloLensView;

PhyloLensViewOptions

| Field | Type | Description | | --- | --- | --- | | container | HTMLElement | Element owned by the host application. PhyloLens mounts the Sigma renderer inside it. | | apiUrl | string | Base URL or path prefix used for /health and /api/graph/* requests. |

Supported apiUrl forms:

| Value | Result | | --- | --- | | "http://localhost:8000" | Direct access to a local service | | "https://api.example.org" | Direct cross-origin service access; the service must allow the host origin through CORS | | "" | Same-origin /health and /api/graph/* routes | | "/phylo-lens" | Same-origin reverse-proxy prefix |

Trailing slashes are normalized. PhyloLens does not add authentication headers or browser credentials.

PhyloLensView

interface PhyloLensView {
  load(options: PhyloLensLoadOptions): Promise<void>;
  exportPng(): Promise<Blob>;
  dispose(): void;
}

load

Prepares and renders a dataset. A call replaces the previously loaded dataset. The returned promise rejects on service, protocol, preparation, or initial viewport failures.

dispose

Unmounts the renderer and invalidates pending work. Repeated calls are safe. Calling load() after disposal rejects.

PhyloLensLoadOptions

interface PhyloLensLoadOptions {
  content: string;
  name?: string;
  sourceFormat?: "newick" | "typing_data";
  metadataSchema?: MetadataField[];
  metadataByNodeId?: Record<
    string,
    Record<string, string | number | boolean | null>
  >;
  ancillaryData?: {
    format: "auto" | "csv" | "tsv";
    content: string;
    join_column: string;
  };
  visualMapping?: VisualMappingOptions;
  layout?: {
    forceIterations?: number;
  };
  lod?: {
    maxNodes?: number;
    lodHint?: number;
    viewport?: Viewport;
  };
}

| Field | Required | Default | Behavior | | --- | --- | --- | --- | | content | yes | — | Raw Newick text or an allelic-profile matrix, according to sourceFormat | | name | no | "uploaded-dataset" | Dataset identifier submitted to the service | | sourceFormat | no | "newick" | Selects direct Newick parsing or PhyloLib typing-data processing | | metadataSchema | no | [] | Declares metadata keys and scalar types | | metadataByNodeId | no | {} | Direct metadata keyed by canonical node ID | | ancillaryData | no | — | CSV/TSV metadata joined by an explicit column | | visualMapping | no | library defaults | Controls node color, size and pie attributes | | lod.maxNodes | no | 6000 | Primary node budget used for viewport requests | | layout.forceIterations | no | — | Reserved by the current public type; not applied by the server pipeline | | lod.lodHint | no | — | Reserved by the current public type; semantic zoom is currently derived from camera ratio | | lod.viewport | no | — | Reserved by the current public type; the initial query is derived from renderer state |

The reserved fields are documented explicitly because they are present in the published TypeScript contract. Applications should not depend on them until runtime behavior is implemented and documented.

Source formats

Newick

await view.load({
  name: "weighted-tree",
  sourceFormat: "newick",
  content: "(A:0.1,(B:0.2,C:0.3)N:0.4)R;",
});

The service accepts one tree or a ;-separated forest. Labels are normalized to stable canonical identifiers. See Input formats for parser behavior and branch-length rules.

Typing data

await view.load({
  name: "mlst-profiles",
  sourceFormat: "typing_data",
  content: [
    "ST\tadk\tfumC",
    "A\t1\t2",
    "B\t1\t3",
    "C\t4\t5",
  ].join("\n"),
});

The service sends the profile matrix through the bundled PhyloLib JAR: Hamming distance is computed first, followed by goeBURST with lvs=3. The resulting Newick tree or forest enters the normal preparation pipeline.

Metadata

Direct metadata

await view.load({
  content: "(P09:1,P12:2)R;",
  metadataSchema: [
    { key: "country", type: "string" },
    { key: "year", type: "number" },
  ],
  metadataByNodeId: {
    p09: { country: "Portugal", year: 2024 },
    p12: { country: "Canada", year: 2023 },
  },
});

Canonical IDs are lowercase slugs of explicit Newick labels. Duplicate labels receive deterministic suffixes.

Ancillary CSV/TSV metadata

await view.load({
  content: "(P09:1,P12:2)R;",
  ancillaryData: {
    format: "tsv",
    join_column: "isolate",
    content: [
      "isolate\tcountry\tsource",
      "P09\tPortugal\thuman",
      "P12\tCanada\tanimal",
    ].join("\n"),
  },
});

join_column is required. The service tries an exact identifier match and then a canonical slug match. When direct metadata and ancillary metadata define the same node field, the direct value takes precedence.

Supporting public types

type SourceFormat = "newick" | "typing_data";

type MetadataType = "string" | "number" | "boolean" | "null";

interface MetadataField {
  key: string;
  type: MetadataType;
}

interface Viewport {
  x: number;
  y: number;
  width: number;
  height: number;
}

Viewport remains exported because it is referenced by the reserved lod.viewport option. The current load path does not use that option to construct the initial API request.

Visual mapping

interface VisualMappingOptions {
  colorField?: string;
  sizeField?: string;
  size?: {
    field?: string;
    scale?: "linear" | "log";
  };
  palette?: string[];
  pie?: {
    enabled?: boolean;
    fields?: string[];
    palette?: string[];
    categoryColors?: Record<string, string>;
  };
}

Behavior:

  • colorField selects a metadata field for frequency-ranked categorical coloring;
  • size.field or the legacy sizeField selects a numeric metadata field;
  • size.scale selects linear or logarithmic scaling;
  • palette overrides the node-color palette;
  • pie controls pie attributes for aggregate nodes.

When no color field is requested, the client prefers region, then the first non-numeric public metadata field. When no size field is requested, it prefers profile_count when available and otherwise uses distance.

Service compatibility errors

The first preparation checks ${apiUrl}/health. Applications may catch the exported errors:

import {
  IncompatiblePhyloLensServiceError,
  PhyloLensServiceProtocolError,
  PhyloLensServiceUnavailableError,
} from "@phyloviz/phylo-lens";

try {
  await view.load({ content: newick });
} catch (error) {
  if (error instanceof IncompatiblePhyloLensServiceError) {
    console.error(error.expectedApiVersion, error.receivedApiVersion);
  } else if (error instanceof PhyloLensServiceUnavailableError) {
    console.error("Service unavailable", error.cause);
  } else if (error instanceof PhyloLensServiceProtocolError) {
    console.error("Invalid /health response", error.cause);
  }
}

Successful compatibility checks are cached per view. Failed checks are not cached, so a later load() can recover after the service is restarted or fixed.

Development

cd code/client
npm ci
npm run dev

The Vite demo runs on http://localhost:3000 and proxies /health and /api to http://localhost:8000. Override the target with:

VITE_PHYLO_LENS_PROXY_TARGET=http://127.0.0.1:8001 npm run dev

Validation commands:

npm run format:check
npm run lint
npm test
npm run build       # reference demo
npm run build:lib   # npm package
npm pack --dry-run

The demo shell is a reference integration and test surface. It is not part of the public package API.