vercel/examples: a plop checklist, a Husky gate, and 39 top level entries
Enjoy our curated collection of examples and solutions. Use these patterns to build your own robust and scalable applications.
At a glance
- What is it?
- Vercel's examples repository is a pnpm monorepo of demo apps rather than a runnable product. New examples come out of plop, every commit passes Husky and lint-staged, and front matter in a README is what turns an example into a draft template.
- Who is it for?
- Use vercel/examples as a pattern source when you want a Vercel shaped demo that already clears someone else's commit gate, and plan to rewrite the parts it leaves open. Read each example's README and package.json against your own project before copying, and pin the layout package yourself, because the newest published release of @vercel/examples-ui is dated 2025-12-12 while the repository itself took commits on 2026-11-02.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 2 days ago.
- What is it written in?
- Mainly TypeScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- vercel/examples5,168 ★ · +7
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| vercel/examples | 5.2k | 5.2k |
7 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The root package is private and has no dev server
The root package.json calls itself `examples`, sets `"private": true`, and exposes four scripts: `lint-staged`, `new-example`, `prepare`, and `prettier`. There is no dev script, no build, no start. The runtime requirements are pinned instead:
"engines": {
"node": "22.x",
"pnpm": "9.13.0"
}`packageManager` repeats pnpm at that exact version, and the only entry under dependencies is `@vercel/sdk` at `^1.18.5`. Everything else sits in devDependencies, where plop `^3.1.1`, husky `^8.0.1`, lint-staged `^13.0.3`, prettier `^2.7.1`, and typescript `^4.9.5` live beside `"eslint": "latest"` and `"eslint-config-next": "canary"`. So the first thing a newcomer does here is install tooling, not start a product:
pnpm i
pnpm new-exampleWhat stands up afterwards is a collection of 39 top level entries rather than a running application, and that gap between the two shapes is worth understanding before copying anything out of this tree.
Husky, lint-staged, and the two globs that decide your commit
Husky manages the pre-commit git hook and configures hooks automatically during install, so a fresh clone already has one. The hook itself is short:
"pre-commit": "lint-staged",
"new-example": "plop example",
"prepare": "husky install"If the hook fails to install, the documented remedy is `pnpm run prepare`, which is the `prepare` script shown above. What lint-staged does with a staged file comes down to two glob keys in the same file. TypeScript and TSX run through Prettier and then through ESLint:
"prettier --write",
"eslint -c .eslintrc.json --no-eslintrc --no-ignore --max-warnings=0 --fix"`--max-warnings=0` is the sharp edge, since one warning stops a commit rather than an error. `--no-eslintrc` sits right next to `-c .eslintrc.json`, so the root config is forced onto files that may carry their own configuration, and `--no-ignore` pulls in paths a normal run would skip. The second glob covers json, md, mdx, css, html, yml, yaml, scss, and vue with Prettier only, so a README rewrite inside an example never meets ESLint. The project asks contributors not to skip these steps unless they are broken, and to open an issue when they are.
The plop template is the checklist a new example has to pass
`pnpm new-example` is a one line alias for `plop example`, and plopfile.mjs plus plop-templates/example hold the shape it generates. Skipping that script is allowed, and then the requirements become a list you check by hand. A `.gitignore` similar to plop-templates/example/.gitignore. A `package.json` similar to plop-templates/example/package.json, with the license set to `MIT` and Next.js usage optional. A `README.md` similar to plop-templates/example/README.md that has to be able to include a demo URL, because the Vercel team will deploy the example. A `.env.example` file plus written instructions on setting the variables up whenever the example needs environment variables, and edge-middleware/bot-protection-datadome is named as the model to copy. A `.eslintrc.json` similar to plop-templates/example/.eslintrc.json if the example uses Next.js. And every Next.js example is expected to use the same styling and layout provided by `@vercel/examples-ui`, whose usage shows up in the plop template itself. The cost of that list is concrete: an example that reads secrets with no `.env.example` teaches the next reader nothing about where the values come from.
Front matter turns a README into a Contentful draft
Adding front matter metadata to the top of an example README is what puts an example in front of users. An example carrying that metadata creates a new Draft template in Contentful, the internal publishing steps live in internal/publishing-templates.md, and the accepted values for each field are listed in internal/fields.json. Cross links between templates reuse the other template's slug: for the monorepo with Turborepo page the slug is `monorepo-turborepo`, written that way in solutions/monorepo/README.md and pasted into the `relatedTemplates` field. The scale of the collection shows in its counters too, at 5,165 stars, 1,843 forks, and 293 open issues. A fork count that size against an open issue count that size is what a gallery people copy from looks like, rather than a library people patch in place.
Go, Python, and Rust folders never meet the ESLint pass
The top level tree carries go/, python/, and rust/ next to app-directory/, apps/, services/, and edge-middleware/, yet the lint-staged routing sends only .ts and .tsx files to ESLint. Prettier handles json, md, mdx, css, html, yml, yaml, scss, and vue. No glob in the file covers .go, .py, or .rs, so a commit that touches nothing but Rust or Go source passes through the hook with nothing run against it. The same table mixes pinned and floating specifiers: prettier is `^2.7.1` and typescript is `^4.9.5`, while eslint is `latest` and eslint-config-next is `canary`. The pnpm-lock.yaml in the tree is what keeps a given clone reproducible, and the engines field pins Node `22.x` with pnpm `9.13.0` so a wrong runtime fails early. In practice this commit hook is a TypeScript gate.
Two front doors and a tree that ranks nothing
Two entry points get named: `/solutions` for demos, reference architecture, and best practices, and `/starter` for functional applications that can act as a starting point. After those two lines the README says only that more exist, then sends readers to the Vercel Templates page for more advanced filtering options. The tree makes the rest concrete, and it is wide: build-output-api/, cdn/, ci-cd/, container-images/, flags-sdk/, framework-boilerplates/, guides/, microfrontends/, storage/, toolbar/, vercel-tutor/, websockets/, plus editor and agent directories such as .agents/, .claude/, .cursor/, .opencode/, and .vscode/. Nothing in that layout ranks anything. Choosing means opening one README and package.json per candidate and reading its dependency list yourself. Those agent and editor directories also show that the root doubles as a working environment for maintainers, not only as a gallery.
The shared layout package does not say which version it pins
Every Next.js example is supposed to share styling and layout from `@vercel/examples-ui`, which makes that package part of the collection's floor. Its published releases are few and far apart: 2.0.1 on 2023-07-17, 2.0.3 on 2023-08-23, and 2.0.4 on 2025-12-12. The repository itself is not idle, with the last push dated 2026-11-02 and no archive flag, so the patterns in this tree keep changing while the shared layout package moves rarely. Check which version of the package a given example's package.json pins before you copy a folder out. The MIT license covers the tree, the primary language is TypeScript, and no project homepage is recorded, so questions and change requests are routed to the repository discussions and pull request pages instead.
Editorial conclusion
Use vercel/examples as a pattern source when you want a Vercel shaped demo that already clears someone else's commit gate, and plan to rewrite the parts it leaves open. Read each example's README and package.json against your own project before copying, and pin the layout package yourself, because the newest published release of @vercel/examples-ui is dated 2025-12-12 while the repository itself took commits on 2026-11-02.
Frequently asked questions
What do I need installed before adding an example to vercel/examples?
Node `22.x` and pnpm `9.13.0`, because the root package.json pins both under `engines` and names [email protected] as the packageManager. After `pnpm i`, the scaffolding command is `pnpm new-example`.
Can I install a package from the vercel/examples repository itself?
No. The root package is named `examples` and marked private, so there is nothing to publish from it. The releases attached to this repository belong to `@vercel/examples-ui`, where 2.0.4 is the newest, published on 2025-12-12.
How does an example in vercel/examples reach the templates page?
Through front matter metadata at the top of its README. An example carrying that metadata creates a Draft template in Contentful, the accepted field values sit in internal/fields.json, and the publishing steps are written in internal/publishing-templates.md.
What does vercel/examples require when my example needs environment variables?
A `.env.example` file plus written instructions on how to set the variables up. The edge-middleware/bot-protection-datadome example is named as the model to follow.
Will the commit hook in vercel/examples reject my work?
It runs Prettier and ESLint over staged TypeScript, and the ESLint call passes `--max-warnings=0`, so warnings block a commit too. If Husky did not install its hook, `pnpm run prepare` installs it.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/vercel-examples)Star history chart for your README
[](https://hysenlabs.com/projects/vercel-examples)Was this useful?