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

@looma/prisma-cli

v0.1.7

Published

Prototype Prisma Compute CLI.

Readme

Prisma CLI Prototype

Prototype npm distribution for the Compute-focused Prisma CLI work in this repo.

Install:

pnpm add -D @looma/prisma-cli

Basic flow:

pnpm prisma-cli auth login
pnpm prisma-cli app deploy --env DATABASE_URL=postgresql://example
pnpm prisma-cli app list-env

Minimal Next.js smoke flow:

pnpm create next-app@latest my-app --yes
cd my-app
# add output: "standalone" in next.config.*
pnpm add -D @looma/prisma-cli
pnpm prisma-cli auth login
pnpm prisma-cli app deploy --app my-app
pnpm prisma-cli app deploy --app my-app --build-type nextjs --http-port 3000

Minimal Bun smoke flow:

mkdir my-bun-app
cd my-bun-app
bun init --yes
pnpm add -D @looma/prisma-cli

Then replace index.ts with a small Bun.serve(...) server and run:

pnpm prisma-cli app build
pnpm prisma-cli auth login
pnpm prisma-cli app deploy --app my-bun-app --env DATABASE_URL=postgresql://example
pnpm prisma-cli app list-env

Notes:

  • the official Prisma ORM package still owns the prisma executable
  • this prototype intentionally exposes prisma-cli so both CLIs can coexist in one app
  • the canonical command shape is still app deploy, not deploy
  • prisma.config.ts is project-only in this prototype and will be created as a plain object export when needed

If you want future-shaped local ergonomics in a test app, add:

{
  "scripts": {
    "prisma": "prisma-cli"
  }
}

Then run:

pnpm prisma app deploy