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

wasp-app-runner-test

v0.0.4

Published

CLI tool for running Wasp applications for headless testing

Downloads

4

Readme

Wasp Application Runner

A robust script to run your Wasp application, including automated database setup and migrations. There are two modes:

  • dev: Runs the Wasp app in development mode using wasp start.
  • build: Builds the Wasp app for production using wasp build and runs it.

When installed, it provides a run-wasp-app command that can be used to run your Wasp app.

Usage

npm install
# Installs wasp-app-runner globally from the local directory
npm run install:global

# Use the `run-wasp-app` command to run your Wasp app
cd /path/to/your/app
run-wasp-app dev

Options

run-wasp-app <mode> [--path-to-app <path>] [--wasp-cli-cmd <command>]

You must pass the <mode> as an argument, which can be either dev or build.

| Option | Description | Example | | ---------------- | ------------------------------------------------------ | --------------- | | --path-to-app | Path to your Wasp application directory (default: ".") | ./my-wasp-app | | --wasp-cli-cmd | Wasp CLI command (default: wasp) | wasp-cli |

Postgres Configuration

Check the ./db/postgres.ts file to see the Postgres configuration used.

If Postgres is used, the script automatically sets the DATABASE_URL env variable for the server app:

DATABASE_URL=postgresql://postgres:devpass@localhost:5432/postgres

Env variables

When using the dev mode:

  • If the app you are trying to run has .env.server or .env.client env files defined, the wasp start will use them as expected.

When using the build mode:

  • run-wasp-app will use the .env.server file when running the server container with Docker locally (which is not done usually by Wasp).
  • .env.client will not be used when building the client, the REACT_APP_API_URL is hard-coded to http://localhost:3001.

Development

When developing, you can run the script directly from the local directory without installing it globally:

npm install
npm run start -- <mode> [--path-to-app <path>] [--wasp-cli-cmd <command>]

npm run start runs npm run build to build the TypeScript code and then runs the ./bin/index.js script.

GitHub Action

This repository also provides a GitHub Action for setting up the Wasp App Runner in your workflows.

Prerequisites

You must set up Node.js before using this action.
e.g. by using actions/setup-node action

- uses: actions/setup-node@v4
  with:
    node-version: 20