About
Universal Server.
Live mirror of the GitHub README. Updated whenever the repo's default branch changes.
λ srvx
Universal Server based on web standards. Works with Deno, Bun and Node.js.
- ✅ Zero dependency
- ✅ Full featured CLI with watcher, error handler, serve static and logger
- ✅ Seamless runtime integration with same API (handler and instance).
- ✅ Node.js compatibility with a close to native performance.
- ✅ Zero overhead Deno and Bun support.
Quick start
export default {
fetch(req: Request) {
return Response.json({ hello: "world!" });
},
};
Then, run the server using your favorite runtime:
# Node.js
$ npx srvx # npm
$ pnpx srvx # pnpm
$ yarn dlx srvx # yarn
# Deno
$ deno -A npm:srvx
# Bun
$ bunx --bun srvx
You can also use srvx fetch to directly call your server handler without starting a server:
$ npx srvx fetch /api/users
See CLI documentation for more options.
👉 Visit the 📖 Documentation to learn more.
Contribution
- Clone this repository
- Install the latest LTS version of Node.js
- Enable Corepack using
corepack enable - Install dependencies using
pnpm install - Prepare stub mode using
pnpm build --stub - Run interactive tests using
pnpm dev
License
Published under the MIT license.
Made by @pi0 and community 💛
🤖 auto updated with automd
Quick facts
npm install srvxHow Sourcemap Explorer detects srvx
We catch srvx from two complementary signals: bundled source paths and the embedded package.json. Modern bundlers (webpack, Vite, esbuild, Rollup, Turbopack) preserve the original node_modules/srvx/ paths inside the JavaScript sourcemap's sources[] array — that's the canonical signal. When the matching package.json is also captured in sourcesContent[], we read the exact version field — patch number included. No regex guessing, no version inference.
- 1
Confirm the site exposes sourcemaps
In DevTools Network, check the response headers of any application script for `SourceMap` or `X-SourceMap`. Failing that, fetch the script's last 4 KB and look for a `//# sourceMappingURL=` comment.
- 2
Find the package in the bundle
Open DevTools → Network → reload. Click any application script and look at its sourcemap. Inside, search `sources[]` for entries matching `node_modules/srvx/` — every match confirms the package is bundled. The matching `sourcesContent[i]` for `node_modules/srvx/package.json` gives you the exact installed version.
- 3
Read the version directly from package.json
Run `jq -r '. as $m | $m.sources | to_entries[] | select(.value | endswith("node_modules/srvx/package.json")) | $m.sourcesContent[.key] | fromjson | .version' bundle.js.map`. Sourcemap Explorer automates the same query in the popup.
Recent versions
FAQ
What is srvx used for?
Universal Server.
How can I tell if a website is using srvx?
Open the page in Chrome with the Sourcemap Explorer extension installed and read the Stack tab. We catch `srvx` from two complementary signals: `node_modules/srvx/` paths inside the JavaScript sourcemap, and the embedded `package.json` we read for exact-version detection. Without the extension you can do the same lookup manually in DevTools — the steps are listed in the "How Sourcemap Explorer detects" section above.
What is the latest version of srvx?
0.11.15, as published on the npm registry. The "Recent versions" table on this page lists the most recent 8 releases with their release dates. Sourcemap Explorer reports the version actually bundled into a site, which can lag the latest release by months on real-world deployments.
Where can I read more?
Project homepage: https://srvx.h3.dev. Source code: https://github.com/h3js/srvx. Published on npm: https://www.npmjs.com/package/srvx. Licensed as MIT.
Detected by Sourcemap Explorer
When a bundle ships sourcemaps, we read the embedded package.json for srvx and report the precise version. Without sourcemaps, an import / require in the page's scripts is enough to flag it.