Vuex vs Pinia: source lines of code compared

The Vuex vs Pinia comparison on OctoCounts shows side-by-side source line counts for vuejs/vuex and vuejs/pinia, counted under the rules and on the dates stated below: files, total lines, code lines, comment lines, blank lines, and per-language totals, pinned to the exact commits listed below.

This page compares the source lines of code (SLOC) of vuejs/vuex and vuejs/pinia using cached OctoCounts reports. Code size is not code quality: a larger count only means more source material, not a better or worse project.

As of 2026-11-09, vuejs/vuex contains 4,905 total lines (3,396 code) across 116 files, while vuejs/pinia contains 26,673 total lines (20,933 code) across 158 files as of 2026-11-10. vuejs/pinia has about 6.2x the counted code lines of vuejs/vuex under the same engine and counting rules. Code size is not code quality: a larger count only means more source material, not a better or worse project.

Metricvuejs/vuexvuejs/pinia
Files116158
Total lines4,90526,673
Code lines3,39620,933
Comment lines6322,900
Blank lines8772,840
Languages counted710

Top languages in vuejs/vuex: JavaScript (77.7% of code), TypeScript (6.5% of code), CSS (4.7% of code). Top languages in vuejs/pinia: YAML (64.1% of code), TypeScript (31.4% of code), JSON (2.3% of code). JavaScript, TypeScript, JSON appear in both top language lists; CSS, HTML appear only in vuejs/vuex's top languages; YAML, Vue appear only in vuejs/pinia's top languages.

Methodology: both counts come from cached OctoCounts reports generated with tokei. vuejs/vuex was counted at ref main (commit bd907467b839) on 2026-11-09; vuejs/pinia was counted at ref v4 (commit 4817135a2543) on 2026-11-10. See the counting methodology for ignored directories and analysis options.

Both reports use the same engine and effective counting rules. Repository declarations, when enabled, are specific to each repository. vuejs/vuex: tokei-15.0.0, policy directories-v1; docs excluded, tests excluded, generated excluded. Excluded directory names: .cache, .generated, .git, .next, __tests__, build, dist, doc, docs, documentation, fixtures, gen, generated, node_modules, target, test, tests, vendor. Ignored languages: none. Repository declarations: off. Exclusions are rule-based; they do not prove that every test, document or generated file was removed. vuejs/pinia: tokei-15.0.0, policy directories-v1; docs excluded, tests excluded, generated excluded. Excluded directory names: .cache, .generated, .git, .next, __tests__, build, dist, doc, docs, documentation, fixtures, gen, generated, node_modules, target, test, tests, vendor. Ignored languages: none. Repository declarations: off. Exclusions are rule-based; they do not prove that every test, document or generated file was removed.

About this comparison

Background observations recorded on 2026-09-16; language descriptions here are historical context, not claims about the current filtered shares. Use this page's measured language breakdown for current counts. Repository layout before counting filters: vuejs/vuex contains Vuex — the state-management library that preceded Pinia in the Vue ecosystem — including its core, tests, and documentation. vuejs/pinia contains Pinia, the state store that the Vue documentation now presents as the default recommendation, with its own core, tests, and docs. Both are Vue-ecosystem state-management source trees, counted on the dates shown above.

The two repositories solve the same problem for the same framework, which makes this one of the more like-for-like comparisons on the site: the counts describe two successive libraries' reading and maintenance surface rather than different layers of a stack.

Both trees are written predominantly in TypeScript as the per-language tables show, reflecting that Pinia was developed in the Vue 3 era and Vuex's later major releases followed the same implementation language.

Line count should not be used to declare a successor or a winner: the Vue documentation's recommendation of Pinia is a project-level statement, and neither the totals nor the language shares are evidence about which store fits a given application.

Sources: vuejs/vuex repository · vuejs/pinia repository. Statements verified 2026-09-16.

Evidence and next steps:

Saved reports remain subject to cache cleanup and replacement. Export their JSON for durable citation; live report URLs can change.

Note: code size is not code quality. OctoCounts only reports reproducible line counts and makes no claim that either project is better.

Compare FAQ

Which has more lines of code, vuejs/vuex or vuejs/pinia?

As of 2026-11-09, vuejs/vuex contains 4,905 total lines (3,396 code) across 116 files, while vuejs/pinia contains 26,673 total lines (20,933 code) across 158 files as of 2026-11-10. vuejs/pinia has about 6.2x the counted code lines of vuejs/vuex under the same engine and counting rules. Code size is not code quality: a larger count only means more source material, not a better or worse project.

Does more source lines of code mean more complexity?

Not necessarily. SLOC measures size, not complexity, quality, or maintainability. A larger codebase can mean more features, more generated or vendored code, more verbose language idioms, or more tests — none of which imply the code is harder to work with. Use SLOC to gauge the scale of what you'd be reading or maintaining, not as a quality signal for vuejs/vuex, vuejs/pinia, or any repository.

How is this comparison calculated?

Methodology: both counts come from cached OctoCounts reports generated with tokei. vuejs/vuex was counted at ref main (commit bd907467b839) on 2026-11-09; vuejs/pinia was counted at ref v4 (commit 4817135a2543) on 2026-11-10. See the counting methodology for ignored directories and analysis options.

Can I compare a different branch, tag, or commit?

Yes. This page shows the default branch for each repository. Use the interactive comparison tool to pick any public GitHub repository, branch, tag, or commit SHA for both sides and get a fresh side-by-side report.