BUG: '...' is often converted to '.' even without --compress

[adamgit]

Description

Many programming languages this is a material change that corrutps the source and fundamentally changes the meaning.

It's annoying that repomix corrutps this.

Usage Context

None

Repomix Version

No response

Node.js Version

No response

[yamadashy]

Hi, @adamgit !
Thank you for reporting this issue!

I couldn't reproduce this problem on my environment. Without the --compress option, Repomix doesn't perform any conversion, so ... should be preserved as-is.

Could you please provide:

1. A minimal code example that reproduces this issue
2. The exact command you're running
3. Your Repomix version

This will help us investigate further.

[adamgit]

My smallest repo is more than 100 files. I think the major issue here is that '...' gets altered at all, even in compress - this is critically significant code in some languages (in typescript it's used very often). This change makes repomix difficult to use with modern LLMs which immediaetly spot "you are using a . where you should have had a spreading operator! That's the source of your problem! I have stopped looking for your bug, you need look no further -- this is definitely the real cause!" -- we have to go in and hand-fix the repomix output, or have a conversation with the LLM to persuad it 'no, that's just a bug in repomix, please ignore the corrupted spreading operators'. Commands used: repomix --ignore "**/*.json,**/*.MD, **/*.xml,**/node_modules,**/data" -o "frontend/repomix-all.xml" repomix --ignore "**/*.json,**/*.MD, **/*.xml,**/node_modules,**/data,**/av" -o "frontend/repomix-all-without-av.xml" version: 1.6.1

…

On Tue, 18 Nov 2025 at 15:10, Kazuki Yamada ***@***.***> wrote: *yamadashy* left a comment (yamadashy/repomix#946) <#946 (comment)> Hi, @adamgit <https://github.com/adamgit> ! Thank you for reporting this issue! I couldn't reproduce this problem on my environment. Without the --compress option, Repomix doesn't perform any conversion, so ... should be preserved as-is. Could you please provide: 1. A minimal code example that reproduces this issue 2. The exact command you're running 3. Your Repomix version This will help us investigate further. — Reply to this email directly, view it on GitHub <#946 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACHL6LYCEWUXHMBI6PEXZD35MZFHAVCNFSM6AAAAACLTVNZEGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKNBYGA3DMMRTGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[yamadashy]

Hi @adamgit,

I cannot reproduce this issue on the latest version (1.9.1). Could you please update and try again?

npm install -g repomix@latest

If the issue persists, please share a small code snippet (with sensitive parts redacted) where ... is being converted to ..

Thank you!

[adamgit]

OK, thanks, I'll update to latest, then keep an eye on it and try to get a narrow example next time it happens.

…

On Mon, 24 Nov 2025 at 06:36, Kazuki Yamada ***@***.***> wrote: *yamadashy* left a comment (yamadashy/repomix#946) <#946 (comment)> Hi @adamgit <https://github.com/adamgit>, I cannot reproduce this issue on the latest version (1.9.1). Could you please update and try again? npm install -g ***@***.*** If the issue persists, please share a small code snippet (with sensitive parts redacted) where ... is being converted to .. Thank you! — Reply to this email directly, view it on GitHub <#946 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACHL6IYU2LC4QOMU4ZOCUL36KROLAVCNFSM6AAAAACLTVNZEGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKNRZGEYTCNZYGQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>