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

@totorototo/navigo

v0.10.1

Published

GPS/geospatial analysis compiled from Rust to WebAssembly — trace, GPX parsing, Minetti pace model, race route analysis (legs/sections/stages), live calibration.

Readme

@totorototo/navigo

GPS/geospatial trace processing — distances, elevation, simplification, climb detection — compiled from Rust to WebAssembly.

Install

npm install @totorototo/navigo

Usage (bundler — Vite, webpack, Rollup)

No manual init() needed; the bundler wires up the .wasm import for you.

import { parseGpx, analyzeGpx, buildTrace } from "@totorototo/navigo";

Usage (plain browser ESM)

import init, { parseGpx, analyzeGpx, buildTrace } from "@totorototo/navigo/web";
await init();

Entry functions

parseGpx(bytes: Uint8Array): Trace | null

Parse a GPX file into a Traceonly <trkpt> track-points are parsed; waypoints and metadata are intentionally skipped so this path stays lean. Returns null when the file contains no valid track-points.

Call parseWaypoints(bytes) and/or parseMetadata(bytes) separately when you need that data, or use parseGpxAll(bytes) to get a Trace with both already attached. If you need the full race analysis in one shot, use analyzeGpx(bytes, options) instead.

const bytes = new Uint8Array(await file.arrayBuffer());
const trace = parseGpx(bytes);

parseGpxAll(bytes: Uint8Array): Trace | null

Parse a GPX file into a Trace that also carries its waypoints and metadata — use this when you'll call .analyze() on the returned handle, since that reads the trace's stored waypoints (plain parseGpx always returns an empty waypoint list). Triple-scans bytes once up front instead of parseGpx's single scan. Returns null when the file contains no valid track-points.

const bytes = new Uint8Array(await file.arrayBuffer());
const trace = parseGpxAll(bytes);

parseWaypoints(bytes: Uint8Array): Waypoint[]

Parse only the <wpt> elements from raw GPX bytes. Returns an array of waypoint objects (empty array when none found).

parseMetadata(bytes: Uint8Array): { name, description }

Parse only the <metadata> block from raw GPX bytes. Returns an object with name and description fields (each null when absent).

trace.analyze(options): object | null

Method on Trace. Compute the race analysis (waypoints, legs, sections, stages) using this trace's waypoints — requires a Trace from parseGpxAll (or analyzeGpx's internal full parse); plain parseGpx traces have no waypoints, so this returns empty legs and null sections/stages. Pure opaque-handle-in, JSON-out — no bytes cross the boundary again, and the expensive trace computation (simplification, elevation, climbs) is never repeated. Returns null on malformed options.

const trace = parseGpxAll(bytes);
const analysis = trace.analyze({
  basePaceSPerKm: 500,
  kFatigue: 0.002,
  lifeBaseStopS: 3600,
});
// analysis.waypoints — Waypoint[]
// analysis.legs      — LegStats[]
// analysis.sections  — SectionStats[] | null
// analysis.stages    — StageStats[] | null
// analysis.metadata  — { name, description }
trace.free();

See options below for the full shape (including optional weather). A Trace built via buildTrace (no GPX source) or plain parseGpx has no waypoints, so .analyze() on either returns an empty legs and null sections/stages.

analyzeGpx(bytes, options): object | null

Convenience wrapper around parseGpxAll + trace.analyze() for callers who just want the JSON result and don't need the Trace handle (so there's no .free() to manage). If you already have a Trace from parseGpxAll, call .analyze() on it directly instead of parsing the bytes twice. Returns null on empty input or malformed options, or the following object:

const result = analyzeGpx(bytes, {
  basePaceSPerKm: 500,
  kFatigue: 0.002,
  lifeBaseStopS: 3600,
});
// result.trace      — TraceSummary
// result.metadata   — { name, description }
// result.waypoints  — Waypoint[]
// result.legs       — LegStats[]
// result.sections   — SectionStats[] | null
// result.stages     — StageStats[] | null

options

| Field | Type | Description | | ---------------- | ---------------- | ------------------------------------------------------ | | basePaceSPerKm | number | Flat-terrain pace in s/km (e.g. 500 = 8:20/km) | | kFatigue | number | Exponential fatigue coefficient (e.g. 0.002) | | lifeBaseStopS | number | Default planned stop at LifeBase checkpoints (seconds) | | weather | WeatherEntry[] | Optional. Per-checkpoint forecast (see below) |

WeatherEntry — matched against waypoint name; unmatched checkpoints use neutral weather (no slowdown):

{ name: string, temperatureC: number, humidityPct: number,
  windKmh: number, precipProbPct: number }
const result = analyzeGpx(bytes, {
  basePaceSPerKm: 500,
  kFatigue: 0.002,
  lifeBaseStopS: 3600,
  weather: [
    {
      name: "Chamonix",
      temperatureC: 32,
      humidityPct: 85,
      windKmh: 35,
      precipProbPct: 80,
    },
  ],
});

TraceSummary

{ totalDistanceKm: number, totalElevationGainM: number,
  totalElevationLossM: number, locationCount: number }

Waypoint

{ latitude: number, longitude: number, elevation: number | null,
  name: string, wptType: string | null, time: number | null,
  stopDuration: number | null }

LegStats

{ legId: number, sectionIdx: number, startIndex: number, endIndex: number,
  startLocation: string, endLocation: string,
  totalDistanceKm: number, totalElevationGainM: number,
  totalElevationLossM: number, avgSlope: number, maxSlope: number,
  minElevation: number, maxElevation: number, bearing: number,
  difficulty: number, estimatedDurationS: number }

SectionStats

{ id: number, stageIdx: number, startIndex: number, endIndex: number,
  startLocation: string, endLocation: string,
  totalDistanceKm: number, totalElevationGainM: number,
  totalElevationLossM: number, avgSlope: number, maxSlope: number,
  minElevation: number, maxElevation: number, bearing: number,
  difficulty: number, estimatedDurationS: number, paceFactor: number,
  startTime: number | null, endTime: number | null,
  maxCompletionTime: number | null, cutoffRatio: number | null,
  stopDuration: number | null }

StageStats — same shape as SectionStats minus stageIdx.

buildTrace(flat: Float64Array): Trace | null

Build a Trace from interleaved coordinates [lon₀, lat₀, alt₀, lon₁, lat₁, alt₁, …]. Returns null when the array carries no points.

const pts = new Float64Array([
  2.350987, 48.856667, 0, 37.617634, 55.755787, 200,
]);
const trace = buildTrace(pts);

Trace

Trace lives in WASM linear memory; the JS object is just a pointer. Always call .free() when done, or use a FinalizationRegistry.

Scalar properties (zero-copy — read from WASM registers)

| Property | Type | Description | | --------------------------- | -------------- | --------------------------------------- | | totalDistance | number | Total distance (km) | | totalElevationGain | number | Cumulative elevation gain (m) | | totalElevationLoss | number | Cumulative elevation loss (m) | | locationCount | number | Number of (D-P simplified) locations |

Array methods (copy WASM → JS heap; call once and cache)

| Method | Returns | Description | | ------------------------------ | -------------- | --------------------------------------- | | getLocationsFlat() | Float64Array | [lon, lat, alt, …] for every location | | getCumulativeDistances() | Float64Array | Distance at each location (km) | | getCumulativeElevationGains()| Float64Array | Cumulative gain at each location (m) | | getCumulativeElevationLosses()| Float64Array| Cumulative loss at each location (m) | | getSlopes() | Float64Array | Slope at each location (%) | | getPeaks() | Uint32Array | Peak location indices | | getValleys() | Uint32Array | Valley location indices |

Methods

indexAtDistance(distKm: number): number

Index of the first location at or beyond distKm.

pointAtDistance(distKm: number): { longitude, latitude, altitude } | undefined

Location object at the given cumulative distance, or undefined.

findClosestPoint(lon, lat, alt): { location, index, distance } | undefined

Nearest location to the given coordinates. distance is in km.

findClosestPointFrom(lon, lat, alt, startFrom): { location, index, distance } | undefined

Like findClosestPoint but only searches from startFrom onwards — use this in live-tracking loops to avoid snapping to an earlier position.

sliceBetweenDistances(startKm, endKm): Float64Array | undefined

All points between two cumulative distances as a flat [lon, lat, alt, …] array, or undefined on invalid input.

getSection(startIndex, endIndex): Float64Array

Points in the index range (inclusive) as [lon, lat, alt, …]. Throws on out-of-bounds input.

area(): { minLongitude, maxLongitude, minLatitude, maxLatitude }

Bounding box of the trace.

elevation(): { positive, negative }

Raw (non-denoised) elevation totals (m).

climbs(): ClimbStats[]

Detected climbs, each with:

{ startIndex: number, endIndex: number, startDistKm: number,
  climbDistKm: number, elevationGain: number, summitElev: number,
  avgGradient: number }

analyze(options): object | null

Race analysis (waypoints, legs, sections, stages) — see trace.analyze(options) above for the full shape and options reference.

free(): void

Release WASM memory. Required — Rust's allocator has no GC bridge.

const registry = new FinalizationRegistry((t) => t.free());
const trace = parseGpx(bytes);
registry.register(trace, trace);

Rust source: https://github.com/totorototo/navigo