Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Keep your lambdas warm during winter. ♨
| Date | Stars |
|---|---|
| 2026-07-24 | 1121 |
| 2026-07-25 | 1121 |
| 2026-07-28 | 1121 |
| 2026-07-30 | 1121 |
| 2026-08-06 | 1121 |
Today
— stars today
This week
— stars this week
This month
— stars this month
Momentum
0.0
growth rate 0.00%/day
# Serverless WarmUp Plugin ♨
[![npm version][npm-version-badge]][npm-version-badge-url]
[![npm monthly downloads][npm-downloads-badge]][npm-version-badge-url]
[](https://github.com/juanjoDiaz/serverless-plugin-warmup/actions/workflows/on-push.yaml)
[![Coverage Status][coveralls-badge]][coveralls-badge-url]
[](https://raw.githubusercontent.com/juanjoDiaz/serverless-plugin-warmup/main/LICENSE)
Keep your lambdas warm during winter.
**Requirements:**
* Node *v20.x* or higher
* Serverless *v3.8* or higher
* AWS provider
## How it works
WarmUp solves *cold starts* by creating a scheduled lambda (the warmer) that invokes all the selected service's lambdas in a configured time interval (default: 5 minutes) and forcing your containers to stay warm.
## Installation
Install via npm in the root of your Serverless service:
```sh
npm install --save-dev serverless-plugin-warmup
```
Add the plugin to the `plugins` array in your Serverless `serverless.yaml`:
```yaml
plugins:
- serverless-plugin-warmup
```
## Configuration
The warmup plugin supports creating one or more warmer functions. Warmers must be defined under `custom.warmup` in the `serverless.yaml` file before they can be used in the functions' configs:
```yaml
custom:
warmup:
officeHoursWarmer:
enabled: true
events:
- schedule: cron(0/5 8-17 ? * MON-FRI *)
concurrency: 10
verbose: true
logRetentionInDays: 14
outOfOfficeHoursWarmer:
enabled: true
events:
- schedule: cron(0/5 0-7 ? * MON-FRI *)
- schedule: cron(0/5 18-23 ? * MON-FRI *)
- schedule: cron(0/5 * ? * SAT-SUN *)
concurrency: 1
verbose: false
testWarmer:
enabled: false
```
The options are the same for all the warmers:
* **folderName** Folder to temporarily store the generated code (defaults to `.warmup`)
* **cleanFolder** Whether to automatically delete the generated code folder. You might want to keep it if you are doing some custom packaging (defaults to `true`)
* **name** Name of the generated warmer lambda (defaults to `${service}-${stage}-warmup-plugin-${warmerName}`)
* **roleName** Name to be applied to the default warmer lambda role. Ignored if a the role setting is used (defaults to `${service.service}-${stage}-${region}-${warmerName.toLowerCase()}-role`)
* **role** Role to apply to the warmer lambda (defaults to a custom role with minimal [permissions](#permissions))
* **tags** Tag to apply to the generated warmer lambda (defaults to the serverless default tags)
* **vpc** The VPC and subnets in which to deploy. Can be any [Serverless VPC configuration](https://serverless.com/framework/docs/providers/aws/guide/functions#vpc-configuration) or be set to `false` in order to deploy the warmup function outside of a VPC (defaults to the vpc in the provider)
* **memorySize** The memory to be assigned to the warmer lambda (defaults to `128`)
* **events** The event that triggers the warmer lambda. Can be any [Serverless event](https://serverless.com/framework/docs/providers/aws/events/) (defaults to `- schedule: rate(5 minutes)`)
* **architecture** The [instruction set to use for the lambda](https://www.serverless.com/framework/docs/providers/aws/guide/functions#instruction-set-architecture) (defaults to `x86_64`)
* **package** The package configuration. Can be any [Serverless package configuration](https://serverless.com/framework/docs/providers/aws/guide/packaging#package-configuration) (defaults to `{ individually: true, patterns: ['!**', '.warmup/${warmerName}/**'] }`)
* **timeout** How many seconds until the warmer lambda times out. (defaults to `10`)
* **environment** Can be used to set environment variables in the warmer lambda. You can also unset variables configured at the provider by setting them to undefined. However, yoExcerpt of 24,265 characters
Read on GitHub
Juanjo Diaz
265
77
6
4
Abe Tomoaki · @clear-code · Japan
4
3
PatrickJS · @kunai-consulting · United States
3
3
2
2
2
2
1
1
1
1
1
1
1
1
Would you bet a product on this? Bounded 0–100 and slow moving.
matched fp:eeee3b48a4767fda, topic:serverless