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

@geopera/sdk

v2.1.0

Published

Official TypeScript client for the Geopera geospatial data platform — fully typed access to every operation.

Readme

@geopera/sdk

npm types License: MIT

The official TypeScript client for the Geopera geospatial data platform — satellite tasking & archive ordering, catalog search, the data platform, billing, and more.

Every capability is an operation at POST /v1/op/{operation_id}. invoke infers the request body and the return type from the operation_id you pass — so calls are checked at compile time and the whole surface tracks the live API by construction. No hand-maintained types, no drift.

  • 🟦 Fully typed by operation_id — wrong body? wrong field? caught at compile time.
  • 🪶 Tiny + dependency-free — one fetch wrapper, ESM + CJS, tree-shakeable.
  • 🌐 Runs anywhere fetch does — Node 18+, Deno, Bun, edge runtimes, the browser.
  • 🔑 Auth your way — a Geopera API key, or an OAuth bearer token from sign-in.

Install

npm install @geopera/sdk
# or: pnpm add @geopera/sdk · yarn add @geopera/sdk

Quickstart

import { GeoperaClient } from "@geopera/sdk";

const geopera = new GeoperaClient({ token: "gpra_..." }); // base URL defaults to https://api.geopera.com

const results = await geopera.invoke("catalog.search", {
  collections: ["sentinel-2-l2a"],
  limit: 10,
});
//    ^? typed as the catalog.search output model

The operation id, the body type, and the awaited result type are all linked: change the id and your editor immediately knows the new body and return shapes.

Authentication

Pass either credential as token; Geopera accepts both and runs every call as that principal (with its scopes, audit, and provenance):

// Headless / server-to-server — a Geopera API key (create one in the portal).
const geopera = new GeoperaClient({ token: "gpra_..." });

// A signed-in user's OAuth bearer token.
const geopera = new GeoperaClient({ token: userAccessToken });

Error handling

A non-2xx response throws a GeoperaError carrying the HTTP status and the RFC 9457 problem+json body Geopera returns for business / permission errors:

import { GeoperaClient, GeoperaError } from "@geopera/sdk";

try {
  await geopera.invoke("orders.tasking.estimate", body);
} catch (err) {
  if (err instanceof GeoperaError) {
    console.error(err.status, err.operation, err.problem);
  }
}

Advanced

// Custom base URL (staging), extra headers, a custom fetch, request cancellation:
const geopera = new GeoperaClient({
  token: "gpra_...",
  baseUrl: "https://staging-api.geopera.com",
  headers: { "X-Request-Source": "my-app" },
  fetch: myFetch, // e.g. undici / a test stub
});

const ac = new AbortController();
await geopera.invoke("catalog.search", { limit: 50 }, { signal: ac.signal });

// One-off without constructing a client:
import { callOperation } from "@geopera/sdk";
const out = await callOperation("organizations.create", { name: "Acme" }, "gpra_...");

Types

OperationId, OperationInput<K>, and OperationOutput<K> are exported for building your own typed helpers. They are derived from the Geopera OpenAPI (regenerate with pnpm gen), the same document that drives the REST API and the Python SDK.

Links

  • 📚 API reference: https://docs.geopera.com/api-reference
  • 🌐 Geopera: https://geopera.com
  • 📦 npm: https://www.npmjs.com/package/@geopera/sdk

License

MIT © Geopera