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

@wasm-idle/llvm-core

v1.0.0-next.0

Published

Browser LLVM runtime hosts for wasm-idle

Vulnerabilities

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

Links

Maintainers

seoriiseorii

Keywords

Readme

@wasm-idle/llvm-core

Browser-side LLVM runtime hosts used by wasm-idle. This package contains JavaScript and TypeScript code only. Compiler modules, sysroots, archives, and other runtime assets must be deployed separately and supplied through explicit HTTP(S) URLs.

import { createClangCompiler } from '@wasm-idle/llvm-core/clang';

const compiler = await createClangCompiler({
	runtimeBaseUrl: new URL('https://cdn.example.com/llvm/clang/')
});

The corresponding compiler patches, source pins, and reproducible asset producers are maintained in the wasm-llvm repository. This package does not read files from that repository or its npm package.

The wasm-idle sync step deterministically repackages the producer's single-entry archives as native gzip delivery assets. Clang uses memfs.wasm.gz, clang.wasm.gz, lld.wasm.gz, and sysroot.tar.gz; COBOL uses cobc.wasm.gz, rootfs.tar.gz, and c-sysroot.tar.gz. The browser loader pipes gzip response bodies through DecompressionStream('gzip'). Runtime manifests from older external deployments may still reference ZIP files; those load fflate only on the legacy compatibility path.