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 🙏

© 2026 – Pkg Stats / Ryan Hefner

create-allwright

v0.2.0

Published

Create a new allwright test project with npm init allwright.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

atmnkatmnk

Keywords

allwrightcreateinitializernpm-inittesting

Readme

create-allwright

Create a new allwright test project with:

npm init allwright@latest

Or:

npm create allwright@latest

The initializer prompts for:

  • TypeScript or JavaScript
  • one or more surfaces such as Web, Mobile Android, Mobile iOS, Desktop macOS, and Desktop Windows
  • an optional target directory

It scaffolds a Node project with package.json, Vitest config, shared allwright config, starter tests, and a short README for the generated app.

Select Mobile iOS interactively, or scaffold it non-interactively:

npm init allwright@latest ios-tests -- --yes --ios

Select Desktop macOS interactively, or scaffold a macosApp project non-interactively:

npm init allwright@latest macos-tests -- --yes --macos

Select Desktop Windows interactively, or scaffold a windowsApp project non-interactively:

npm init allwright@latest windows-tests -- --yes --windows

Use --all to scaffold Web, Mobile Android, Mobile iOS, Desktop macOS, and Desktop Windows together. The repeatable --surface flag supports the ids web, mobile-android, mobile-ios, desktop-mac, and desktop-windows for explicit combinations.

This writes an iosApp starter test and configures the public universal Simulator IPA at https://allwright.dev/Flights-simulator.ipa. On the first test run, core installs the mobile-ios plugin and its bundled headless XCTest agent, then the fixture downloads and installs the sample app. Users do not install either component manually.

The Desktop macOS starter configures the installed Calculator app and writes a lazy macosApp screenshot test. Its first run installs desktop-mac, starts a locally signed copy of the bundled XCUITest runner, and launches Calculator. It requires macOS 14 or newer, Xcode, and UI Automation permission for the process running Xcode.

The Desktop Windows starter configures Notepad and writes a lazy windowsApp screenshot test. Its first run installs desktop-windows and starts the bundled, self-contained FlaUI UIA3 agent. It requires an interactive Windows 10 or newer desktop session; no separate Appium, WinAppDriver, or .NET installation is needed.

Dependencies are installed automatically with the package manager that ran the initializer. Existing lockfiles take precedence; use --package-manager npm|yarn|pnpm|bun to override detection, or --no-install to scaffold without installing.