TodoMVC compares frameworks by one spec, and on purpose ships unminified
Helping you select a JavaScript framework - Todo apps for React.js, Angular, Vue and many more
At a glance
- What is it?
- TodoMVC is the same todo application implemented across the popular JavaScript frameworks against a single app spec, so syntax and structure can be compared side by side, with seven examples kept current in 2.0 and a markdown spec written to be handed to a coding agent. Its own disclaimer rules out two things people keep trying to read into it: capability comparisons and bundle size comparisons.
- Who is it for?
- TodoMVC fits a team about to pick a framework and wanting twenty minutes of real code per option, and it fits an agent workflow now that app-spec.md can be pasted straight into a prompt. It does not fit a decision about bundle size, because the examples are unminified on purpose, and it does not settle questions about state management at scale, because the behavioural surface stops at add, edit, toggle, filter, route and clear completed.
- Can I use it commercially?
- Check first. The repository uses a licence we do not classify automatically, so read its LICENSE file before any commercial use.
- Is it still maintained?
- Yes. The repository last received commits 162 days ago.
- What is it written in?
- Mainly JavaScript, 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
- tastejs/todomvc28,974 ★ · +19
| Repository | 2026-09-28 | 2026-11-15 |
|---|---|---|
| tastejs/todomvc | 29k | 29k |
19 Stars in the last 48 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
One spec, and the behavioural surface is deliberately small
The comparison works because everything except the framework is held still. Each example is functionally identical and follows the same app specification in `app-spec.md`, so what differs between two directories is syntax, structure and idiom, and nothing else.
The surface is worth knowing because it is the limit of what these examples can tell you. Every app implements add, edit, toggle, filter, route and clear completed, and the project's own disclaimer says a todo application offers a limited view of a framework's potential capability. It is meant as a gateway to reviewing how a basic application may be structured, with a heavy recommendation to research a chosen solution in depth before committing.
So read the directory listing as a map of the first hour with a framework, not as a feature matrix. What transfers to a real codebase is the shape of the code, not the coverage.
Seven examples track current stable lines
The maintained set in TodoMVC 2.0 is specific about versions: React 19, Vue 3.5, Angular 21, Svelte 5 with runes, Preact 10, Lit 3.3, and React Redux 9 with Redux Toolkit 2. Those are the directories kept current with each framework's latest stable line.
Everything else in `examples/` is a legacy example kept for historical reference, and the list is long enough to make the point: angular-dart, aurelia, backbone in three variants, binding-scala, canjs, closure, dojo, emberjs, gwt, javascript-es5, javascript-es6, jquery and more. The website carries the full list.
The practical rule for a reader is to check the version in the directory you are about to copy from. A syntax example from a legacy directory can teach you an idiom that a current release has since replaced, and nothing in the directory name tells you which era it belongs to.
Each example builds and serves itself
There is no monorepo build to learn. Each example is a self-contained project, most of them on Vite, webpack or rollup, and you work inside the directory you want to read:
$ cd examples/react
$ npm install
$ npm run build
$ npm run serveThe README gives this as the general pattern for each example: cd into it, install, and run.
The cost is that there is no shared dependency install. Comparing seven frameworks means seven `npm install` runs and seven dev servers, and comparing all of `examples/` means doing that for every legacy showcase as well. The root package exists to serve the site and run the tests, not to orchestrate the examples.
Cypress defaults to the curated set, and --all sweeps the museum
The test suite is a Cypress run against the maintained examples, started through `start-server-and-test` on `http://localhost:8000`:
$ npm install
$ npm run test:all`test:all` defaults to the curated modern set. Pass `--all` to sweep every example in `examples/`, or `--framework=react` to target a single one, and `tests/README.md` has the details. The scripts behind it are visible in package.json, where `server` runs `node tests/server.js`, `cy:open` opens the Cypress runner, and `cy:run` is the headless path.
One consequence to plan around: `--all` is a sweep, not a supported configuration. Frameworks in the legacy example directories are pinned to their own toolchains of the era, and the README frames the default set as the curated one, so a failure under `--all` says more about an old example than about the suite.
The root still carries Bower, gulp and jshint from the 1.x era
The repository root tells two stories at once. There is a modern layer: `cypress.config.js`, a `cypress/` directory, `tests/`, `server.js` on Express 5, and package scripts that assume Node 20.19.0 or newer.
And there is the older one. `bower.json` and a `bower_components/` directory sit at the root next to `gulpfile.js`, `tasks/`, `.jshintrc`, `.jscsrc`, `.jshintignore`, `test-runner.sh`, `.travis.yml` and `circle.yml`. The team section even credits a past migration of all the apps to Bower as a contribution, which dates that layer.
For a contributor the rule is simple: do not read the root tooling as the tooling the maintained examples use. Each example carries its own. A pull request that runs the root jshint configuration is testing something the current examples never load.
Unminified on purpose, so size comparisons are off the table
The disclaimer is unusually direct and worth reading before quoting anything from this repository. TodoMVC has been called the speed-dating and the Rosetta Stone of JavaScript frameworks, and the project asks that you keep the limits in mind: it is not the perfect way to compare the size of different frameworks, because the unminified versions are used intentionally to make the source code easier to read.
That is a design decision with a clear cost. You cannot learn from this repository which framework ships the smaller bundle, because every example is deliberately un-shrunk. Any size figure you take from here is an artefact of a decision made for readability.
The other half of the disclaimer is about capability. A todo app exercises state, routing and rendering and almost nothing else, so it says little about server rendering, data loading, form complexity or the ecosystem around a framework. It is a first impression with real code in it, which is what it is meant to be.
2.0.0 shipped on 2026-06-06, after a two-year gap
The release history explains the two-era repository. Version 1.3.1 is dated 2018-08-23 with the release name Build Passing, v1.4 follows on 2024-01-16, and 2.0.0 lands on 2026-06-06, the same day as the last push recorded for the repository. It is not archived.
So the Bower-era layout in the root and the npm-and-Cypress layout in the maintained examples are two releases apart, and a reader arriving today meets both at once. The README describes the curated set of seven as of TodoMVC 2.0.
A second thread runs through the project and is easy to miss. The README states that TodoMVC forms the core of the cross-browser Speedometer benchmark, which is used by browser engines to optimise UI performance, and the site itself is served from this repository alongside the examples. The teaching project and the benchmark share code.
Editorial conclusion
TodoMVC fits a team about to pick a framework and wanting twenty minutes of real code per option, and it fits an agent workflow now that app-spec.md can be pasted straight into a prompt. It does not fit a decision about bundle size, because the examples are unminified on purpose, and it does not settle questions about state management at scale, because the behavioural surface stops at add, edit, toggle, filter, route and clear completed. Use the maintained seven, read the disclaimer before quoting any comparison, and check release 2.0.0 from 2026-06-06 against the 1.x Bower-era examples still sitting in the same directory.
Frequently asked questions
What is TodoMVC used for?
It is a comparison tool: the same todo application implemented in most popular JavaScript frameworks, with each example functionally identical and following the same app spec, so you can compare syntax, structure and idioms. Its examples also form the core of the cross-browser Speedometer benchmark.
Which frameworks are actively maintained in TodoMVC 2.0?
React 19, Vue 3.5, Angular 21, Svelte 5 with runes, Preact 10, Lit 3.3, and React Redux 9 with Redux Toolkit 2. Plenty of legacy examples remain in examples/ for historical reference, and the website carries the full list.
How do I run a TodoMVC example locally?
Change into the example directory and use npm, since each example builds and serves itself on Vite, webpack or rollup: `cd examples/react`, then `npm install`, `npm run build` and `npm run serve`. There is no shared root build across the examples.
How do I run the TodoMVC tests?
Run `npm install` and then `npm run test:all`, which starts the server on http://localhost:8000 and runs the Cypress suite against the curated modern set. Add --all to sweep every example or --framework=react to target one, and see tests/README.md for details.
Can I use TodoMVC to compare framework bundle sizes?
No. The project states it is not the perfect way to compare the size of different frameworks, because the unminified versions are used intentionally to make the source code easier to read.
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/tastejs-todomvc)Star history chart for your README
[](https://hysenlabs.com/projects/tastejs-todomvc)Was this useful?