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

@sr-connect/runtime-types

v2.1.0

Published

Types for ScriptRunner Connect runtime

Readme

@sr-connect/runtime-types

TypeScript declarations for the globals available inside the ScriptRunner Connect script runtime.

The package ships a single index.d.ts and no runtime code. It is consumed by the ScriptRunner Connect code editor and by the local development tooling, so scripts get type checking and autocompletion for everything the runtime injects on top of the language itself.

What the runtime provides

Scripts run against ECMAScript 2020 (lib: ["es2020"] in tsconfig.json). There is no DOM and no Node.js standard library. require() does not exist and process.env is always empty; environment variables come from context.environment.vars.

On top of the core language the runtime adds these globals, all declared in this package:

  • console with log, debug, info, warn, error, trace, assert, counters, timers and groups. Output goes to the invocation logs.
  • fetch() together with Request, Response, Headers, Blob, FormData, URL and URLSearchParams. RequestInit.agent accepts TLS client certificates and custom CA bundles. The whole response body is downloaded before the promise resolves.
  • crypto (also reachable as window.crypto) with getRandomValues() and a subset of SubtleCrypto: key generation, import, export, sign and verify. Encryption, digests and key derivation are not implemented.
  • TextEncoder and TextDecoder.
  • setTimeout, clearTimeout, setInterval, clearInterval, btoa, atob and performance.now().
  • ServiceError, thrown by the runtime and the managed API clients when a service call fails, and AbortProcess.
  • AbortController and AbortSignal as stubs: they track state and notify listeners, but fetch() ignores signal, so aborting never cancels a request.
  • Context, the object passed to the script entry point as its second argument. It carries the invocation id, start time, timeout, available memory, environment details and variables, trigger type, deployment info and queue details for queued invocations.

Where behaviour differs from browsers or Node.js the JSDoc on the declaration says so. Examples: performance.now() returns seconds, Headers matches names case-insensitively but keeps the casing each name was first set with instead of lower-casing it, and a Body can be read once.