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

@swiftbrowser/wasm-sdk

v0.17.8

Published

The Swift SDK for WebAssembly's base, for the Swift compiler built as WebAssembly (@swiftbrowser/wasm-compiler): the WASI sysroot, clang's headers and the Swift standard library (Swift 6.4.0, wasm32-unknown-wasip1).

Vulnerabilities

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

Links

Git

Maintainers

dabbottdabbott

Keywords

Readme

@swiftbrowser/wasm-sdk

What every compile reads: wasi-libc and libc++'s archives, clang's and the Swift runtime's headers, and the standard library's modules and archives (Swift, Concurrency, Observation, Synchronization, string processing).

One of the packages that carry the Swift SDK for WebAssembly (swift-6.4.0-RELEASE_wasm) for SwiftBrowser, split by who needs which files:

| Package | Contents | | --- | --- | | @swiftbrowser/wasm-sdk | the WASI sysroot, clang's headers, the standard library | | @swiftbrowser/wasm-sdk-foundation | Foundation and CoreFoundation | | @swiftbrowser/wasm-sdk-icu | lib_FoundationICU.a without its data member | | @swiftbrowser/wasm-sdk-icu-data | ICU's whole data package | | @swiftbrowser/wasm-sdk-testing | XCTest and Swift Testing | | @swiftbrowser/wasm-sdk-cxx | libc++'s headers and C++ interop |

Each keeps its files at their paths in the SDK's wasm32-unknown-wasip1 directory, and lists them in files.json, so the SDK is the packages laid over each other. @swiftbrowser/cli does that when it compiles with the Swift compiler built as WebAssembly and no Swift is installed (swiftbrowser doctor --install), and SwiftBrowser's playground fetches the files it needs from them. The files are the SDK's, unchanged but for ICU's data moving out of its archive; the dynamic-linking libraries, Embedded Swift and the modules' documentation are left out. See LICENSE.txt for the licenses of what they contain.