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

sst-warmer

v0.1.1

Published

Extends SST SsrSites with an optional warming feature. Applies to RemixSite, SvelteKitSite, AstroSite, and SolidStartSite.

Readme

sst-warmer

This is a simple package that simply extends an SsrSite construct from SST and allows you to keep a specified number of functions warm. Keeping lambdas warm can help with cold starts and the benefits are most evident when the lambda's bundle size is large, read more about how warming works and the associated costs in this post by Open Next.

If you want to keep any of the following SST-deployed sites warm than this package is for you!

  • RemixSite
  • SvelteKitSite
  • AstroSite
  • SolidStartSite

If you want to keep a NextjsSite warm then you are in luck! This is already supported via SST, see the documentation to learn more.

This package exists only to bridge the gap unil this issue is closed, note that a PR is out already here as well. The API for this package matches exactly with the PR referenced above, so when SST supports this natively you can seamlessly remove this package and upgrade. I mostly just wanted to speed my site up in the meantime and figured I would package this up & share as it was a request feature in the SST discord.

Installation

npm install sst-warmer

Usage

This package is pretty simple, just ensure that you have the appropriate peer dependencies installed:

  • "aws-cdk-lib": ">=2.24",
  • "constructs": ">=10.1.0",
  • "sst": ">=2.11.16"

Then you can import the "warm" version of the site you want to create, and use it. Since this packages declares sst as a peer dependency it should be compatible with any version of SST so long as you meet the peer dependency requirements, this also means it will be a drop in replacement for your current site construct with the only difference noticable is the added warm prop.

// This was your old construct ...
import { RemixSite } from "sst/constructs";

const site = new RemixSite(stack, "web", {
  path: "packages/web/",
  customDomain: app.stage === "prod" ? domainName : undefined,
  cdk: { server: { architecture: Architecture.ARM_64 } },
  environment: SiteEnv,
});

// .. and this is the construct with warming
import { RemixSite } from "sst-warmer";

const site = new RemixSite(stack, "web", {
  path: "packages/web/",
  customDomain: app.stage === "prod" ? domainName : undefined,
  cdk: { server: { architecture: Architecture.ARM_64 } },
  environment: SiteEnv,
  warm: 5, // + we will keep 5 lambda warm
});