Skip to content

v1.16.1

Latest

Choose a tag to compare

@yamadashy yamadashy released this 11 Jul 12:36
Immutable release. Only release title and notes can be modified.

This release is a bug-fix patch: it plugs a WebAssembly memory leak, extends comment removal to more JavaScript/TypeScript module files, and fixes the token count tree for underscore-prefixed directories and the directory tree on Windows. Updating to 1.16.1 is recommended for all users.

Improvements ⚡

Fixed a WebAssembly Memory Leak (#1681)

Parsed web-tree-sitter Tree objects were not released after use, leaking WebAssembly heap memory when parsing or compressing many files — noticeable on large repositories. Each tree is now freed right after parsing, keeping memory usage stable.

Special thanks to @isaka1022 for their first contribution! 🎉

Comment Removal for More Module Files (#1683)

--remove-comments now strips comments from JavaScript/TypeScript module files that were previously skipped — .mjs, .cjs, .mts, .cts, and their JSX variants .mjsx / .mtsx.

repomix --remove-comments

Special thanks to @serhiizghama for this contribution! 🎉

Token Count Tree: Count Underscore-Prefixed Directories (#1710)

Directories whose names start with an underscore (for example __tests__ or __mocks__) were dropped from the --token-count-tree output and excluded from the token totals. They are now rendered and counted like any other directory.

repomix --token-count-tree

Special thanks to @serhiizghama for this contribution! 🎉

Correct Directory Tree and File Ordering on Windows (#1712)

On Windows, the <directory_structure> section collapsed into a flat list of full paths and file sorting fell back to a plain string comparison, because already-normalized (/-separated) paths were being split on the OS separator (\). Paths are now normalized before splitting, so the tree nests correctly and files sort in directory-aware order on every platform.

Special thanks to @serhiizghama for this contribution! 🎉

How to Update

npm update -g repomix

As always, if you have any issues or suggestions, please let us know on GitHub issues or our Discord community.