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

@mostlyrightmd/weather

v1.17.0

Published

Weather data for TypeScript / Node — live METAR (AWC), ASOS archive (IEM), historical observations (GHCNh), and NWS climate text products (CLI). For quants, ML training pipelines, and weather-bot agents. Direct public-API access, no hosted backend.

Downloads

1,072

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

helloiamvuhelloiamvu

Keywords

weatherweather-dataweather-apimetarasosnoaanwsnws-cliawciemghcnhforecastobservationsclimate-dataweather-stationweather-botml-training-datatime-seriestypescriptnodejs

Readme

@mostlyrightmd/weather

Weather data fetchers and parsers for the mostlyright TypeScript SDK — live METAR (AWC), ASOS archive (IEM), IEM CLI, historical observations (GHCNh), NWS climate text products (CLI), plus the local-first cache layer — for quants, ML training pipelines, and weather-bot agents. Direct public-API access; no hosted backend, no API key. Mirrors the Python mostlyrightmd-weather distribution. Declares @mostlyrightmd/core as a peer dependency.

Install

pnpm add @mostlyrightmd/weather @mostlyrightmd/core

Docs

See https://mostlyright.md/docs/sdk/quickstart-typescript/ for a 60-second quickstart, or the full API reference at https://mostlyright.md/docs/sdk/.

What's NOT in the TypeScript SDK (yet)

  • forecastNwp() is a typed stub in v1.x. Gridded NWP forecasts (HRRR, GFS, NBM, …) require GRIB2 decode, which depends on native libraries (eccodes / cfgrib) that don't run in browser or Node.js without an impractical WASM bundle. The function signature is stable — you can write code today that keeps working when v2.0+ lands the execution body. Calls throw NwpNotAvailableError (subclass of DataAvailabilityError).
  • climateGaps() is a typed stub in v1.x. Climate cache is server-only (GHCNh CSVs are 10+ MB per station-year).

For gridded NWP today, use the Python SDK — mostlyrightmd-weather ships 11 NCEP-family models (HRRR, GFS, NBM, RAP, RRFS, …) end-to-end. See docs/nwp-forecasts.md for the architectural rationale, workaround paths, and v2.0+ roadmap.

For the 7 major US stations with IEM MOS coverage (KNYC, KLAX, KORD, KMIA, KDEN, KSEA, KATL), iemMosForecasts() ships today as the recommended TS-side workaround.

The 1.17 registry redesign — what changed for TypeScript

The Python SDK's 1.17 release introduces the align / spine / sources ladder (mr.align(spine, *sources), per-domain pairs(), the .label. axis). The TypeScript surface you use is unchanged in 1.17: research() / dataset() keep working exactly as before. The new ladder verbs (align / spine / pairs) are Python-only on 1.17 — the async TS align() is deferred and tracked as parity ticket PT-3401 (see .planning/CROSS-SDK-SYNC.md). The shared cross-SDK conformance fixtures (tests/fixtures/parity/conformance/) are the standing acceptance gate for when the TS aligner lands.

Full symbol-move and where-did-each-kwarg-go tables: docs/migration/v117-align-spine-sources.md.