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-pollar-app-patrickkish

v0.1.7

Published

Scaffold a Next.js app with Pollar wallet pre-wired

Downloads

103

Readme

create-pollar-app-patrickkish

Scaffold a Next.js 16 app with Pollar wallet already wired — login, balance, assets, send, receive, and transaction history via the official SDK.

Built for pollar-backoffice#2.

Quick start

The issue acceptance path is npx — it works for everyone regardless of which package manager you use in the generated app.

npx (primary — issue #2 flow)

npx create-pollar-app-patrickkish@latest my-pollar-app
cd my-pollar-app
# edit .env.local — set NEXT_PUBLIC_POLLAR_API_KEY=pub_testnet_...
npm run dev

Non-interactive:

npx create-pollar-app-patrickkish@latest my-pollar-app --yes --pm pnpm --network testnet

Use --pm to pick the package manager for the new app (defaults to npm when invoked via npx).

pnpm (team preference)

pnpm dlx create-pollar-app-patrickkish@latest my-pollar-app
cd my-pollar-app
# edit .env.local — set NEXT_PUBLIC_POLLAR_API_KEY=pub_testnet_...
pnpm dev

Non-interactive:

pnpm dlx create-pollar-app-patrickkish@latest my-pollar-app -- --yes --pm pnpm --network testnet

npm

Equivalent to npx (no npx prefix needed):

npm create create-pollar-app-patrickkish@latest my-pollar-app
cd my-pollar-app
# edit .env.local
npm run dev

Non-interactive:

npm create create-pollar-app-patrickkish@latest my-pollar-app -- --yes --pm npm --network testnet

yarn

yarn create create-pollar-app-patrickkish my-pollar-app
cd my-pollar-app
# edit .env.local
yarn dev

Non-interactive:

yarn create create-pollar-app-patrickkish my-pollar-app --yes --pm yarn --network testnet

bun

bunx create-pollar-app-patrickkish@latest my-pollar-app
cd my-pollar-app
# edit .env.local
bun run dev

Non-interactive:

bunx create-pollar-app-patrickkish@latest my-pollar-app --yes --pm bun --network testnet

What you get

The generated app includes:

  • Next.js 16 App Router, React 19, TypeScript, Tailwind 4
  • @pollar/core@^0.9.0 and @pollar/react@^0.9.0
  • PollarProvider in the root layout
  • Login via Pollar's hosted modal (Google, email OTP, passkey, external wallets)
  • Home screen actions that open SDK modals: balance, assets, send (USDC example), receive, history
  • .env.example, eslint, prettier, and a README with a Deploy to Vercel button

No backend and no secret keys — client-side only.

CLI flags

| Flag | Description | |------|-------------| | --yes / -y | Skip prompts (uses detected package manager + testnet) | | --pm <npm\|pnpm\|yarn\|bun> | Package manager for installing the new app | | --network <testnet\|mainnet> | Written to .env.local as NEXT_PUBLIC_POLLAR_NETWORK |

When you skip --pm, the CLI picks the manager that invoked it (pnpm dlx → pnpm, npm create → npm, etc.).

Environment variables

| Variable | Required | Description | |----------|----------|-------------| | NEXT_PUBLIC_POLLAR_API_KEY | Yes | Publishable key from dashboard.pollar.xyz (pub_testnet_...) | | NEXT_PUBLIC_POLLAR_NETWORK | No | testnet (default) or mainnet |

Get a testnet key at dashboard.pollar.xyz → Configuration → API Keys.

Requirements

  • Node.js 20+
  • A Pollar publishable API key (free, self-serve)

Develop this package locally

git clone https://github.com/PatrickKish1/create-pollar-app-patrickkish.git
cd create-pollar-app-patrickkish
pnpm install
node bin/index.js my-test-app --yes --pm pnpm

Publish to npm

This package must be public so reviewers and users can run npx / pnpm dlx without npm login:

npm publish --access public

Do not use --access private for this deliverable — a private package cannot be installed by maintainers testing issue #2.

A prepublishOnly script blocks publishing if node_modules exists inside template/.

License

MIT