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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@swizzyweb/swerve-manager

v0.1.9

Published

swizzy-swerve is a bootstrapper for swizzy web services. This package will bootstrap and run independent swizzy web services.

Readme

swerve

swizzy-swerve is a bootstrapper for swizzy web services. This package will bootstrap and run independent swizzy web services.

Docs

https://swizzyweb.github.io/swerve-manager/

Supported commands

swerve: synonym for swerven

swerven: swerve with nodejs

swerveb: swerve with bun

swerved: swerve with deno

swervenc: swerve with node clustered

swervebc: swerve with bun clustered

swervedc: swervice with deno clustered.

Usage:

npm run server <port (optional>

Or install globally:

npm install -g .

Uninstall

npm uninstall -g @swizzyweb/swerve

Command

swerve

Swerve can run multiple packages on the same port using a single command. Just provide multiple package names space separated.

run

swerve <service> [seriveB serivceC...] [options]

run clustered

swervec <service> [--numThreads (optional)] [options]

Note: cluster commands end with c

options


--port : (default 3005) port value to run service
--appDataRoot - (default project root) path to where appdata root directory will be placed, stores logs and service data
--numThreads - (default num cpu's reported by os) (cluster only) number of threads to use in the cluster
--<argKey> - Any additional key passed will be a serviceArg passed to all services

ie:


swerve some-service-name --port=3000

No args

This will run the project in the current working directory


swerve

Current dir with port

This will run the server in the current directory with the specified port


swerve .

with port:


swerve . --port 3000

Run single file


swerve /path/to/file.js

ie:


swerve /absolute/path/to/app.js

or


swerve $(pwd)/dist/app.js

Additional runtimes

We support bun deno and nodejs for runtimes


swerven # node
swerveb # bun
swerved # deno

swerven # default (points to swerven as of 0.2.4)

cluster

to run a cluster of your swerve services, you can use the cluster scripts. These are implemented in nodejs, bun, and deno.

default cluster


swervec

nodejs cluster


swerven

bun cluster


swervebc

deno


servedc

What's passed to getWebservice in web service package

{
packageName: string,
port: number,
app: expressApp,
logger: ILogger,
appDataPath: "/appDataRoot/appdata/serviceName/"
...serviceArgs // Anything else (from service config or swerve command args)
}

Service Configurations

{
  "port": 3000, // Global port
  "services": {
    "friendlyLocalServiceName": {
      "port": 3001, // Optional port override
      "servicePath": ".", // if building package in current directory
      "myArg1": "AnythingYouWant" // Custom serviceArg
    },
    "friendlyImportServiceName": {
      "port": 3002,
      "packageName": "@swizzyweb/dyn-serve-web-service" // running installed web service package
    },
    "friendlyNeighborServiceName": {
      "port": 3002,
      "servicePath": "../my-friendly-neighbor-web-service",
      "authCode": "SomeAuthCode"
    }
  }
}

Running

swerve --config my-web-service-config.json

Generate Docs

npx typedoc