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

@lingxia/rong

v0.3.1

Published

TypeScript type definitions for Rong JavaScript runtime

Readme

@lingxia/rong

TypeScript type definitions for the Rong JavaScript runtime (globals injected by Rust).

Scope

  • Provides .d.ts/TS sources for the runtime surface so editors/TS can typecheck Rong scripts.
  • Not a runtime polyfill: it does not provide implementations, only types.

Runtime Export Map (high level)

  • Rong namespace: file system, storage, runtime metadata, command APIs, timer helpers, compression helpers, and host constructors such as RedisClient, S3Client, SQLite, and SSE
  • Globals added by Rong modules include fetch, assert, atob, btoa, Worker, setTimeout, clearTimeout, setInterval, and clearInterval
  • Additional Web-standard globals such as Request, Response, Headers, FormData, URL, ReadableStream, WritableStream, Blob, File, AbortController, and DOMException are also provided when the corresponding runtime modules are enabled

The type package relies on TypeScript’s DOM libs for shared Web API base types.

Installation

npm install @lingxia/rong

Usage (typechecking only)

Add to your tsconfig.json:

{
  "compilerOptions": {
    "types": ["@lingxia/rong"]
  }
}

Notes:

  • This enables global typings; you should not import runtime modules like 'http' (those are Rong globals, not Node modules).
  • Ensure your tsconfig.json lib includes "DOM" if you want DOM globals (e.g. URL, ReadableStream) to be typed.
  • Worker uses the DOM global type name. The package exports RongWorker/RongWorkerMessageEvent/RongWorkerErrorEvent for the precise Rong subset when you want stricter annotations.
  • Rong’s runtime Storage constructor intentionally is not redeclared globally in the type package, because the DOM lib already owns the global Storage name. Use the exported Storage/StorageConstructor types as local annotations when needed.
  • The package only supports the root export @lingxia/rong; src/* and dist/* are not public import paths.

Accuracy notes (common gotchas)

  • Storage is not localStorage-compatible. The standard runtime exposes new Storage(path, options?); embedders may also inject a preconfigured storage instance, but that is not part of the default runtime surface.
  • Directory listing is Rong.readDir(...) (async iterator), not Rong.readdir(...).
  • HTTP is the global fetch(...) API. There is no http namespace and no download JS API.

Development

# Install dependencies
npm install

# Build
npm run build

# Watch mode
npm run watch