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

@le-space/browser

v0.1.52

Published

Shared browser-safe Aleph deployment and polling helpers.

Readme

@le-space/browser

This package is the browser/PWA-facing shared layer for reusable Aleph deployment primitives.

It is intended to sit between:

  • @le-space/core
  • @le-space/rootfs
  • browser applications such as deployment PWAs

The package should stay UI-neutral. It provides browser-safe helpers, but it does not own app-specific Svelte state, prepaid enforcement policy, or wallet UX.

Client Surface

The preferred public entrypoint is a typed browser client factory:

  • createAlephBrowserClient({ apiHost?, crnListUrl? })

That client should remain small and stable. It currently owns:

  • balance lookup
  • CRN listing
  • instance listing
  • 2n6 web access lookup
  • message envelope lookup
  • scheduler allocation lookup
  • CRN execution list lookup and normalization
  • CRN allocation notify
  • relay setup-server configure request
  • deployment result inspection and polling
  • Aleph message broadcast helpers

Lower-level helper functions remain exported too, but new extractions should prefer hanging reusable behavior off the client surface unless there is a good reason to keep them as standalone utilities.

The package also exports lower-level browser/EVM helpers for:

  • ethCall
  • sendTransaction
  • personalSign
  • prepaid vault reads and transaction helpers

Planned v1 Scope

The package currently covers:

  • http.ts
    • fetchWithTimeout
  • aleph-api.ts
    • balance fetch
    • CRN fetch
    • instance listing
    • Aleph message broadcast helpers
    • deployment polling and result inspection
    • scheduler and CRN runtime lookup helpers
  • client.ts
    • typed browser client factory
  • rootfs.ts
    • RootFS manifest load
    • RootFS existence check
    • RootFS reference resolution
  • pricing.ts
    • instance pricing fetch and parse helpers
  • evm.ts
    • ethCall
    • sendTransaction
    • personalSign
  • prepaid.ts
    • reusable prepaid vault protocol helpers

Not In Scope Initially

These should remain local to apps until the browser package has a stable base:

  • wallet-provider integrations
  • prepaid enforcement policy and wallet UX
  • UI-only formatting helpers
  • Svelte state orchestration

Source Of Truth

The detailed extraction roadmap lives in:

  • docs/docusaurus/docs/architecture/browser-extraction-plan.md