serverless-express
Run Express and other Node.js frameworks on AWS Serverless technologies such as Lambda, API Gateway, Lambda@Edge, and more.
Runssource: GitHubhomepageJavaScriptApache-2.0commit 4205db8998b3
JavaScript, Apache-2.0 licensed. The project labels itself: alb, api gateway, aws, aws lambda, aws serverless, dynamodb, express and express js.
serverless-express runs. An Argusic agent installed it in 0.5 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
@codegenie/serverless-express v5.0.0 installs, all 12 Jest test suites pass (228 passed), and manual E2E confirms Express app wrapper correctly processes API Gateway v1/v2 events returning HTTP 200 responses.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 95 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Node v18.19.1 in container is below required >=24. Engine warnings on install for undici and unicorn-magic.
- Install time
- under a minute
- Cold machine to finish
- 3 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- npm test: 12 suites, 228 passed, 5 skipped. Manual smoke: node -e 'const express=require("express"); const sls=require("./src/index"); ...', handler returned 200 with correct JSON body for GET and POST requests on both API Gateway v1 and v2 events.
- Model tokens used
- 35,666
- Exact commit tested
- 4205db8998b3
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
succeeded in 3617ms: Test Suites: 12 passed, 12 total Tests: 5 skipped, 228 passed, 233 total Snapshots: 0 total Time: 2.472 s, estimated 3 s exec /bin/sh -lc 'npx tsc ./src/*.ts --outDir typescript-out --noEmit --strict 2>&1' in /work/repo succeeded in 7923ms: TypeScript type checking on the `.d.ts` files passed cleanly too. Here's the final report. tokens used 35,666 TypeScript type checking on the `.d.ts` files passed cleanly too. Here's the final report.
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 0.5 minutes.
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 0.5 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
albapi-gatewayawsaws-lambdaaws-serverlessdynamodbexpressexpress-jsexpressjshacktoberfestlambdanodenode-jsnodejssamserverlessserverless-applicationsserverless-expressserverless-frameworkvendia
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/serverless-express)Questions
- Does serverless-express run?
- Yes. serverless-express runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test serverless-express?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 4205db8998b3. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test serverless-express?
- The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does serverless-express take to install?
- 0.5 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does serverless-express need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing serverless-express?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for serverless-express?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.