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

@tschk/moonshine-deploy-vercel

v0.4.49

Published

Vercel deployment adapter for Moonshine.

Vulnerabilities

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

Links

Maintainers

undivisibleundivisible

Keywords

Readme

@tschk/moonshine-deploy-vercel

Vercel deployment adapter for Moonshine.

import { vercelAdapter } from "@tschk/moonshine-deploy-vercel";

await vercelAdapter.build(manifest, ".moonshine");
  • Target runtimes: node, vercel-edge.
  • Capabilities: streaming, islands, edge.
  • Output: .vercel/output with static HTML, function directories, and config.json route regexes.

Limitations: static catch-all routes are not pre-rendered; each non-static route becomes a separate function; revalidation is not supported.

See docs/DEPLOYMENT.md and docs/MANIFEST.md.

Native manifests support only the Node runtime. The adapter bundles one standalone Node 22 function (index.mjs) containing the native renderer and route modules. Build Output filesystem routing serves public client assets first, then sends requests through the complete loader/action/middleware pipeline, including routes marked static. No React or Solid runtime is included. For native builds, only files within the build's public directory can enter Vercel static output. Legacy explicit external asset registrations remain supported, while the build's dist directory and registered server entry are excluded.

Native Edge, request context, islands/hydration, and cache/revalidation options are rejected. Local acceptance runs the relocated function under actual Node HTTP with a small filesystem-routing harness; this does not emulate Vercel infrastructure or establish a public deployment. Legacy rendering requires the optional @tschk/moonshine-react peer.