Source: https://seerepo.com/compare/sampotts/plyr/vs/vercel/next.js
Markdown source: https://seerepo.com/compare/sampotts/plyr/vs/vercel/next.js.md
Description: plyr and next.js share 3 technologies: Tailwind CSS, PostCSS, and Sass. Both are written in JavaScript.

# plyr vs next.js

plyr and next.js share 3 technologies: Tailwind CSS, PostCSS, and Sass. Both are written in JavaScript.

- [sampotts/plyr](https://seerepo.com/r/sampotts/plyr): Deprecated in favour of Video.js 10; security updates only. Simple HTML5, YouTube and Vimeo player.
- [vercel/next.js](https://seerepo.com/r/vercel/next.js): The React Framework

## What they share and what sets them apart

- In common: Tailwind CSS, PostCSS, Sass
- Only in plyr: Autoprefixer, cssnano, postcss-custom-properties
- Only in next.js: React, Express, concurrent-queue, Tokio, scheduler, Next.js, react-server-dom-webpack, styled-jsx, emotion, geist, MUI, react-virtualized, Framer, Headless UI, @heroicons/react, Lucide, Cheerio, js-yaml, image, sharp, prop-types, Ajv, tracing, tracing-subscriber, OpenTelemetry, pino, class-variance-authority, next-themes, tailwind-merge, Radix UI, cmdk, prompts

## Side by side

| | plyr | next.js |
|---|---|---|
| Size | 10,582 lines written, 41 code files | 2,391,614 lines written, 5,697 code files |
| Who writes it | 0.5% of its commits signed by AI. With Claude Code | 0.8% of its commits signed by AI. With Claude Code, Cursor, GitHub Copilot, and Devin |
| Activity | Last push October 21, 2026, 1,832 commits, 29,990 stars | Last push November 4, 2026, 36,392 commits, 143,262 stars |
| Tests | 0 test files | 18,587 test files. 6.5% of its code files have a test that imports them |

- Size: Lines written by people and agents, without generated ones; code files, without tests.
- Who writes it: A commit counts as AI's when it carries its signature: a Co-Authored-By line, its author name or the merge of its branch.
- Activity: From GitHub and its history, on the day SeeRepo read it.
- Tests: The files that test the code, and the share of code files a test imports.

## Frequently asked questions

### Which is bigger, plyr or next.js?

next.js, with 2,391,614 lines written; plyr has 10,582.

The proof: [vercel/next.js's code at commit 97f1a2c](https://github.com/vercel/next.js/tree/97f1a2c8a1deb23cf03855d67f942c0fe3ded1ce)

### Which has more GitHub stars, plyr or next.js?

next.js, with 143,262 stars; plyr has 29,990.

The proof: [vercel/next.js on GitHub](https://github.com/vercel/next.js)

### Which has more tests, plyr or next.js?

next.js, with 18,587 test files.

The proof: [vercel/next.js's code at commit 97f1a2c](https://github.com/vercel/next.js/tree/97f1a2c8a1deb23cf03855d67f942c0fe3ded1ce)

### Which was updated more recently, plyr or next.js?

next.js: its last push was on November 4, 2026, and plyr's on October 21, 2026.

The proof: [vercel/next.js's commits on GitHub](https://github.com/vercel/next.js/commits)

### Which has more commits signed by AI, plyr or next.js?

next.js: an AI signed 0.8% of its commits, with Claude Code, Cursor, GitHub Copilot, and Devin; in plyr, 0.5%.

The proof: [the commits each tool signed in vercel/next.js](https://seerepo.com/r/vercel/next.js/ai)

## Sources

- sampotts/plyr: Read on November 8, 2026, at commit b23f9b7 (https://github.com/sampotts/plyr/tree/b23f9b7d52366d171ed4ec45bd06aedd85954486)
- vercel/next.js: Read on November 4, 2026, at commit 97f1a2c (https://github.com/vercel/next.js/tree/97f1a2c8a1deb23cf03855d67f942c0fe3ded1ce)

## What is your repo built with?

Any public repo, with no account: https://seerepo.com/r/owner/repo/built, with the owner and name it has on GitHub.