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

@dev-audit/gitignore-generator

v0.1.4

Published

Detects your project stack and generates a tailored .gitignore file

Readme

@dev-audit/gitignore-generator

Detects your project stack and generates a tailored .gitignore file automatically.

Supported Stacks

  • Node.js
  • Next.js
  • Python
  • Docker
  • Terraform
  • Go
  • Rust
  • Java / Maven / Gradle

Multi-stack projects are handled automatically — a Next.js project gets both the Next.js and Node.js entries combined.

Usage

Via the full dev-audit suite (recommended):

# Preview the generated .gitignore (dry run)
npx dev-audit gitignore generate

# Write the .gitignore to disk
npx dev-audit gitignore generate --write

Or run without installing:

npx @dev-audit/gitignore-generator generate --write

Or install globally:

npm install -g @dev-audit/gitignore-generator
dev-audit-gitignore generate --write

What gets generated

For a Next.js project the output includes:

# Next.js
.next/
out/
.vercel
next-env.d.ts
*.pem

# Node.js
node_modules/
npm-debug.log*
yarn-debug.log*
yarn-error.log*
.pnpm-debug.log*
dist/
build/
coverage/
*.tsbuildinfo
.env*
!.env.example

# OS
.DS_Store
Thumbs.db

# Editors
.vscode/
.idea/

.env* covers all env files while !.env.example keeps your example file tracked. OS and editor entries (.DS_Store, .vscode/, .idea/) are always appended regardless of stack.

How stack detection works

The tool checks for well-known indicator files at the project root:

| Stack | Detected by | |---|---| | Next.js | next in package.json deps, next.config.js/ts | | Node.js | package.json present | | Python | requirements.txt, Pipfile, pyproject.toml, setup.py | | Docker | Dockerfile, docker-compose.yml | | Terraform | main.tf, terraform/ directory | | Go | go.mod | | Rust | Cargo.toml | | Java | pom.xml, build.gradle |

Contributing

npm test
npm run lint
npm run format

Minimum coverage threshold: 80%