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

@bishoymly/start

v0.4.0

Published

Create an agent-ready Next.js workspace from the terminal or a portable web blueprint.

Vulnerabilities

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

Links

Git

Maintainers

bishoymlybishoymly

Keywords

Readme

@bishoymly/start

Create a focused, agent-ready Next.js workspace from the terminal or from a blueprint made at bishoy.io/start.

pnpm dlx @bishoymly/start@latest

With no blueprint, the CLI asks the same project, UI, service, and delivery questions as the web builder. Its first choice can open the web builder instead, or you can open it directly:

pnpm dlx @bishoymly/start@latest --web

Commands copied from the web builder remain deterministic and non-interactive:

pnpm dlx @bishoymly/start@latest my-app --blueprint v2.<token>

Start refuses to overwrite non-empty directories and rejects absolute or parent-traversing paths.

Every generated workspace includes strict TypeScript, Tailwind CSS v4, shadcn/ui source components, an agent instruction hierarchy, a high-quality README, .env.example, and Git setup. A pinned design reference is optional. The UI contract carries a normalized shadcn preset plus a minimal, top-navigation, or sidebar starting surface. Preset commands pasted into either builder are decoded as data and are never executed.

The blueprint can independently add Biome or ESLint with Prettier, CI, Vitest, Playwright, OpenTelemetry, Sentry, Better Auth, Drizzle or Prisma, storage, and AI providers. Review also provides a tailored, copyable kickoff prompt for the selected coding agent after the deterministic scaffold command runs.

Only selected integrations are written or installed. --skip-install still produces the complete workspace contract without installing dependencies. When Playwright is selected and installation is enabled, the CLI also installs the pinned Chromium browser so the generated verify command is ready to run.

Blueprint v1 is intentionally unsupported in v0.4. Rebuild older configurations at bishoy.io/start.

Links

Development

npm install
npm test

Start is released under the MIT License.