Repository navigation
v1.0.13
sizeofvar v1.0.13 Changelog
Release Date: October 2026
Release Type: Patch
Branch: next → master
Overview
A dev-tooling dependency patch. Three development dependencies move to their current releases: @cldmv/fix-headers, which maintains the comment headers at the top of the repository's source, test, config and workflow files, from 2.1.1 to 2.2.0; @cldmv/configs, the package that supplies the shared fix-headers configuration, from 1.2.0 to 1.2.4; and the @cldmv/vitest-runner test runner from 1.2.0 to 1.5.3. No runtime code changed: sizeofvar.js is exactly as in v1.0.12, and the package still has no runtime dependencies.
The fix-headers bumps were made with a header restamp in mind, but neither produced any header change in this repository: running npm run fix:headers against this release rewrites 0 files, so the only files touched are package.json and package-lock.json, plus the documentation described below.
🔧 Dependencies
All of these are dev dependencies. The lockfile changes are limited to the packages below, the package's own version, and the one transitive package the test runner pulls in (chalk).
@cldmv/fix-headers^2.1.1→^2.2.0(resolved 2.1.1 → 2.2.0; #32 moved it to 2.1.4 and #37 to 2.2.0). The 2.1.4 release no longer stamps a header into files that have no usable comment syntax (strict JSON such aspackage.json, and Markdown unless explicitly forced), never walks intonode_modulesor other dependency folders, and processes every repeated--inputvalue instead of only the last. The 2.2.0 release changes what@Last modified bymeans: it now names whoever last edited a file's content, so a run that only rewrites a header (a date format conversion, a corrected@Project, new spacing) keeps the recorded editor instead of claiming the file for whoever ran the tool. The 2.1.2 and 2.1.3 releases in between were repository-maintenance releases with no change to the tool. It only runs through thefix:headersscript; nothing that ships depends on it.@cldmv/configs^1.2.0→^1.2.4(#37)..configs/fix-headers.jsonextends@cldmv/configs/fix-headers.json, and from 1.2.4 that shared config setsforceAuthorUpdateandforceLastModifiedAuthorUpdatetofalse(both weretruein 1.2.0). Together with fix-headers 2.2.0, afix:headersrun no longer overwrites@Authoror@Last modified byon every file.@cldmv/vitest-runner^1.2.0→^1.5.3(#35), the test runner. This restores the bump from #27, which merged intonextjust after the previous release and was dropped by the post-release reset ofnext(CLDMV/.github#360); it is reinstalled at the latest version instead of the original 1.5.1. The runner's own Node requirement rises from>=20.19.0to>=22.12.0, and itschalkdependency moves from 5.6.2 to 6.0.1 (Node 22 or later); the runner's package metadata also now declares Apache-2.0 instead of MIT. Test tooling only; nothing that ships depends on it.
📚 Documentation
- NEW: docs/changelog/v1/v1.0.13.md: this changelog.
- Changelogs for earlier releases that shipped without one (v1.0.1 through v1.0.12) were added in the same pass (see the docs/changelog/ folder).
- README: a new What's New section with the Latest release and the four before it.
Upgrade notes
- No breaking changes, and no runtime code changed. It's a drop-in replacement for v1.0.12.
- For contributors: running the test suite now needs Node.js 22.12.0 or later, which is the floor the CI matrix has used since v1.0.9. The package itself declares no
engines, and consumers are unaffected. - For contributors: fix-headers 2.2.0 decides whether a file's content was edited by comparing the working tree with git
HEAD, so runnpm run fix:headersbefore committing, not after.
| Metric | Coverage |
|---|---|
| Statements | 100.0% |
| Branches | 100.0% |
| Functions | 100.0% |
| Lines | 100.0% |
Avg: 100.0% · 256f999 · Node lts/*