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/kit

v0.29.2

Published

SwiftBrowser compiled for WebAssembly, so that @swiftbrowser/cli builds an app's own code only: every module of the Swift package and an archive of its objects (with debug info), for Swift 6.4.0 and its Swift SDK for WebAssembly. Its macros come built as

Vulnerabilities

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

Links

Git

Maintainers

dabbottdabbott

Keywords

Readme

@swiftbrowser/kit

SwiftBrowser compiled for WebAssembly, so that @swiftbrowser/cli builds an app's own code only: every module of the Swift package (@swiftbrowser/swift) and an archive of its objects, with debug info, for Swift 6.4.0 and its Swift SDK for WebAssembly, and its macros (@Model, #Predicate, @Entry) built as WebAssembly. The macros are the same files on every host: @swiftbrowser/wasm-compiler runs them for its own compiler, and for a native toolchain through a small launcher the CLI names as the macros' plugin executables. (Releases up to 0.7 shipped them as executables in one package per host, @swiftbrowser/kit-linux-x64, -linux-arm64 and -darwin-arm64.)

The CLI depends on it, at its own version: there is nothing to import or configure. On the first dev or build it copies the kit into its cache (~/.cache/swiftbrowser/kits/), checks that the installed toolchain reads its modules, and builds every app against it. When it cannot use the kit (another toolchain, or Windows, where the compiler cannot run the launcher) it compiles SwiftBrowser once itself, as it would without this package. See the CLI's README.

kit.json names the shim the kit was built from (the id the CLI computes from @swiftbrowser/swift's sources), the toolchain and SDK, and the modules with their dependencies; wasm32-unknown-wasip1/Modules holds the compiled modules (the Mac-only ones, AppKit, under its macOS/, on the search path of a build for macOS alone) and wasm32-unknown-wasip1/lib their archives. The release workflow builds it (swiftbrowser kit, then pack-kit.mjs); the contents are not in the repository.