Detect Webpack in any GitHub repo

webpack is the long-standing JavaScript module bundler with a huge loader and plugin ecosystem.

Why show Webpack on your README

Knowing a project is still on webpack matters to contributors used to Vite or Turbopack; the card surfaces it from the config file.

How Webpack is detected

Stack Fingerprint reads the repo's full file tree in one GitHub API call and flags Webpack when it finds any of these:

  • Files or folders: /^webpack\.config/
  • Dependencies in package.json: webpack

Webpack README badge

A static badge you can paste anywhere in Markdown:

Webpack badge

Markdown
![Webpack](https://img.shields.io/badge/Webpack-8DD6F9?style=for-the-badge&logo=webpack&logoColor=white)

Or let the repo describe itself

Static badges go stale the moment you swap a dependency. A Stack Fingerprint card is generated from the repo, so Webpack (and everything around it) appears or disappears on its own:

Tech stack card for webpack/webpack
webpack/webpack · generated live from the repo
README.md
[![Stack Fingerprint](https://stackfingerprint.vercel.app/api/card?repo=OWNER/REPO)](https://stackfingerprint.vercel.app/?repo=OWNER/REPO)

Replace OWNER/REPO with your repository, or open the builder to pick a theme and layout.