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

@oxc-project/runtime

v0.158.0

Published

Oxc's modular runtime helpers

Vulnerabilities

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

Links

Git

Maintainers

boshenboshen

Keywords

Readme

Oxc's modular runtime helpers

Vendored from the complete published @babel/[email protected] package, including all 95 CommonJS/ESM helper pairs and Babel's MIT license. All credits to the Babel team.

upstream.json records the upstream version, SHA-256 of every upstream helper file, and the local patches. The tests check these hashes so unrecorded edits cannot silently diverge from Babel.

Differences from Babel

  • setFunctionName.js and esm/setFunctionName.js preserve "[]" for Symbol(""), matching native computed method names. Babel 8.0.8 returns an empty name. These files are unchanged from Oxc's existing helpers and are the only patches to the upstream helper tree.
  • Oxc retains its three TypeScript legacy decorator helpers: decorate, decorateParam, and decorateMetadata. They are adapted from TypeScript and are absent from Babel 8.
  • The 26 older Babel helpers removed in Babel 8 remain available for compatibility with previously generated code. Their names are listed in upstream.json; they are outside the Babel 8 source snapshot.
  • Package identity, Oxc's version and Node.js requirements, and the src/ layout remain Oxc-specific. Babel's export targets and sideEffects: false are synchronized while preserving Oxc's existing conditional-export precedence; explicit helpers/esm/* and older package exports remain supported.

Updating

Download and extract a specific published version of @babel/runtime, then run from this directory:

node scripts/sync.mjs /path/to/extracted/babel-runtime

The script copies every unpatched upstream helper and the license, updates exports and the hash manifest, and preserves compatibility helpers and recorded local patches. Before writing, it checks that each patched helper still matches its recorded local hash and that its upstream source is unchanged. If upstream changes a patched helper, the script stops so its local changes can be reviewed against the new version.

The manifest uses the script's generated JSON formatting and is excluded from repository formatting. Repeating the command with the recorded upstream version leaves the runtime tree unchanged. Tests reconstruct that upstream tree offline, using the vendored helpers and the original sources of the two patched helpers.

Run the import, integrity, and runtime behavior tests with:

node --run test