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

@astroscope/hyperspace

v0.1.3

Published

Pre-compressed in-memory static file serving for Astro — save space, serve from hyperspace

Readme

@astroscope/hyperspace

Note: This package is in active development. APIs may change between versions.

Pre-compressed in-memory static file serving for Astro SSR. Save space, serve from hyperspace.

CDNs and reverse proxies often compress on the fly with conservative settings — or sometimes not at all. Hyperspace pre-compresses static files at build time with maximum brotli and gzip quality, then serves them from memory at startup. The result is smaller responses than most CDNs produce in real-time, with zero per-request CPU or disk overhead. Works great standalone or behind a proxy.

Examples

See the demo/hyperspace directory for a working example.

Installation

npm install @astroscope/hyperspace

Usage

// astro.config.ts
import { defineConfig } from 'astro/config';
import hyperspace from '@astroscope/hyperspace';

export default defineConfig({
  output: 'server',
  integrations: [hyperspace()],
});

That's it. No configuration needed.

What it does

Build time

After Astro finishes building, hyperspace walks dist/client/ and compresses every text-based static file:

  • Brotli at maximum quality (level 11)
  • Gzip at level 9
  • Skips variants where compressed size >= original size
  • Writes .br and .gz files next to originals

Compressible extensions: .html, .css, .js, .mjs, .json, .xml, .svg, .txt, .wasm, .map, .webmanifest, .xhtml

Runtime

On server startup, the middleware loads all compressible files and their pre-compressed variants. When a request comes in, it:

  1. Checks if the request path matches a cached file
  2. Negotiates encoding from Accept-Encoding (prefers br > gzip > raw)
  3. Returns the best variant from memory with correct headers
  4. Falls through to Astro for non-static requests

Headers

  • Content-Encoding: br or gzip when serving compressed
  • Vary: accept-encoding on all cached responses
  • Cache-Control: public, immutable, max-age=31536000 for /_astro/ files (hashed filenames)

Memory footprint

Typical memory usage is modest:

| Site size (raw) | Estimated memory (raw + br + gz) | | --------------- | -------------------------------- | | 400 KB | ~600 KB | | 3 MB | ~5 MB | | 10 MB | ~15 MB |

Only text-based files are loaded. Images, fonts, and other binaries are left to Astro's default static file handling.

Dev mode

In development, there are no compressed files — the middleware gracefully no-ops and passes all requests through to Astro.

Requirements

  • Node.js runtime
  • SSR output mode (output: "server")

License

MIT