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

@pulse-compute/assets

v1.0.0-beta.10

Published

Package-owned asset lowering facade and compiler integration for Pulse.

Vulnerabilities

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

Links

Git

Maintainers

nw.isnw.is

Keywords

Readme

@pulse-compute/assets

Support tier: Supported provider/extension surface Audience: Applications using JavaScript asset middleware or the package-owned lowerable asset lookup capability. Install directly: Yes, only when the application uses the assets capability. Supported entry points: @pulse-compute/assets Stability: The package root is the supported JavaScript API and canonical Native authoring surface, including bounded embedded Assets bytes on their qualified targets. /pulsewasm remains a compatibility subpath; manifest/compiler subpaths are toolchain integration. No application binary inspection is exposed. npm: @pulse-compute/assets Canonical documentation: Package guide

This release-status block is generated from the synchronized Pulse 1.0.0-beta.10 package policy.

The normal package root is the supported JavaScript API and canonical Native authoring surface:

import { assets } from '@pulse-compute/assets'

const found = await assets.lookup(ctx, 'public', '/app.js', { method: 'GET' })
return assets.respond(found)

assets.lookup() is a request-bound package effect owned by the internal pulse.assets contract and may be directly awaited or included in ctx.parallel({ ... }). JavaScript executes the actual package implementation; supported Native calls are recognized by the trusted package compiler and lowered to assets.lookup.

The same root exports createAssets, AssetManager, AssetBucket, and signSigV4 for direct JavaScript local, hosted, and S3-compatible asset middleware. Hosted and bucket modes preserve upstream Web response streams. Local mode follows the restored reference behavior; a broader resource-bound policy belongs at the shared core request/response boundary.

@pulse-compute/assets/pulsewasm remains a compatibility-only lowerable facade. Direct JavaScript execution of that subpath throws PulseWasmAssetsLoweringError; applications should use the normal package root. Manifest and compiler exports are toolchain integration. Migration guidance is published at https://pulsecompute.io/v1.0.0-beta.10/guides/compatibility-imports/.