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

@wral/hurricane-tracker

v0.1.1

Published

Lit web component that renders an Atlantic hurricane tracker from api-wxdata, using Leaflet + MapLibre GL.

Downloads

220

Readme

@wral/hurricane-tracker

<wral-hurricane-tracker> — Lit web component that renders an active Atlantic hurricane tracker using api-wxdata v2 storm data, drawn on a Leaflet map with a MapLibre GL vector-tile basemap.

Replaces the legacy iframe at webapi.wral.com/api/html/30 (which wrapped Baron's mapv2 widget). All data comes from https://api.wral.com/wxdata/v2/hurricanes/active.

Usage

<wral-hurricane-tracker
    basin="atlantic"
    refresh-seconds="0"
    wxdata-base="https://api.wral.com/wxdata/v2"
    style-url="https://demotiles.maplibre.org/style.json"
></wral-hurricane-tracker>

<script type="module" src=".../define.standalone.js"></script>

Attributes

| Attribute | Default | Description | |---|---|---| | basin | atlantic | Storm basin to track. Passes through to wxdata. | | wxdata-base | https://api.wral.com/wxdata/v2 | Base URL for the wxdata endpoint. | | refresh-seconds | 0 | Auto-refetch cadence in seconds. 0 disables auto-refresh. | | style-url | WRAL's MapTiler style (matches wral.com/dashboard) | MapLibre style URL. Defaults to WRAL's custom MapTiler style for visual consistency across surfaces. Override for local dev / alternate environments. |

Builds

  • Library: dist/index.mjs + dist/define.mjs. Consumer bundles lit, leaflet, maplibre-gl, and @maplibre/maplibre-gl-leaflet.
  • Standalone: dist/define.standalone.js. Single file with all deps inlined; drop into any page via <script type="module" src="…">.

Development

npm install
npm run dev      # Vite playground at http://localhost:5173/
npm run lint
npm run build    # both lib + standalone outputs in dist/

Data shape

The component reads /hurricanes/active?basin=<basin> and expects:

{
    "data": {
        "basin": "atlantic",
        "count": 0,
        "storms": [
            {
                "name": "Erin",
                "classification": "TS",
                "position": {"lat": 25.1, "lon": -74.8},
                "max_winds": 55,
                "min_pressure": 1002,
                "movement": {"direction_deg": 320, "speed": 18},
                "track": [{"lat": ..., "lon": ...}, ...],
                "forecast": [{"lat": ..., "lon": ..., "time": "…"}, ...],
                "cone": [[lat, lon], ...]
            }
        ],
        "season": {"year": 2026, "named_storms": 0, "hurricanes": 0}
    }
}

If the live shape differs (e.g. cone as GeoJSON), the parsing in src/map.mjs is the single place to adjust.