Josh Pike

I don't mean to pressure. I appreciate the work you guys are doing, and will just bear with it. If I could code in Rust I would have contributed already...

Oh wow I didn't know! I'm sorry to hear about it. Despite the situation I'm sticking with it, even with the current issues it's still a breath of fresh air...

I ran in the same root directory as my node_modules folder, which has Rome installed. The globs are relative to the same path whether run from script, or from terminal....

Ok so the situation is now even more bonkers. one of my developers ran the exact same code from his terminal: ```node_modules/rome/bin/rome ci client/src/**/*.ts --colors=force``` It only says it's checked...

There's clearly an issue with how the glob argument is being processed, that glob should definitely be picking up more than 13 files, it seems to not be treating the...

this no longer seems to be a problem for us, @geekmidas maybe your problem is due to you using a more advanced glob syntax. Maybe need to create a new...

reopened as now I found how to make it happen. if running from terminal, I get the right amount. Checked 335 file(s) in 63ms Found 27 error(s) if I run...

same problem if I'm using child.exec

running this from terminal works correctly: ```node_modules/rome/bin/rome ci client/src/**/*.ts --colors=force``` Running that same command in a node.exec or spawn command from a script based in the _same directory_ that I...

more simple case: - use the shelljs library - test.js below: ``` import shell from 'shelljs'; shell.exec('node_modules/rome/bin/rome ci client/src/**/*.ts --colors=force'); ``` ^ only scans the files in client/src/*.ts, does not...