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

patra-turbo-template

v1.1.6

Published

Scaffold a new project from the turbo-template monorepo (Next.js, Express, WebSocket, Prisma, Tailwind)

Readme

patra-turbo-template

Scaffold a new Turborepo monorepo from the turbo-template (Next.js, Express, WebSocket, Prisma, Tailwind).

Layout: Both the npm package and the template live under template/:

  • template/create-turbo-template/ – this package (publish to npm)
  • template/turbo-template/ – the monorepo template (source for scaffolding)

What to do next

  1. Bundle the template into the package (so it’s included when you publish):

    cd template/create-turbo-template
    bun run copy-template

    This copies ../turbo-template into ./template (creates template/create-turbo-template/template/ with the app).

  2. Test locally (from any empty folder):

    node path/to/template/create-turbo-template/cli.js my-test-app
    cd my-test-app && bun install && bun run dev
  3. Publish to npm
    Open a terminal, go into this package folder, then run:

    cd path/to/CI_CD/template/create-turbo-template
    npm login
    npm publish

    (Replace path/to/CI_CD with your actual path, e.g. C:\Users\patra\Desktop\Devops_prac\CI_CD on Windows.)
    prepublishOnly will run copy-template again before packing, so the tarball always has an up-to-date template/.

Usage (after publish)

npx create-turbo-template my-app
cd my-app
bun install
bun run dev

Or with npm:

npm create turbo-template@latest my-app
cd my-app
bun install
bun run dev

Publishing to npm

  1. One-time: copy the template into the package

    cd create-turbo-template
    bun run copy-template

    This copies ../turbo-template into ./template (excluding node_modules, .git, etc.).

  2. Publish

    • If you don’t have an npm account: npmjs.com
    • npm requires two-factor authentication (2FA) to publish. Enable it at npmjs.com → Account → Security.
    • Login: npm login
    • Publish (choose one):
      • Unscoped (name must be free): npm publish
      • Scoped (e.g. @yourusername/turbo-template): change "name": "create-turbo-template" to "name": "@yourusername/create-turbo-template" in package.json, then npm publish --access public
  3. Later: after changing turbo-template

    • Run bun run copy-template again in create-turbo-template
    • Bump version in package.json (e.g. 1.0.1)
    • Run npm publish

What gets created

  • apps/web – Next.js (port 3000)
  • apps/http-server – Express API (port 3002)
  • apps/ws-server – WebSocket server (port 3001)
  • packages/db – Prisma + PostgreSQL
  • packages/ui – Shared React components
  • packages/eslint-config, packages/typescript-config – Shared configs