Closed k2snowman69 closed 3 years ago
I suspect that is how glob works, as we use glob to match files for us. You can probably specify glob configuration to address this, see:
https://github.com/adamreisnz/replace-in-file#specify-glob-configuration
Or your work around, as mentioned. Let me know if you think the problem lies with the package instead of glob.
I'm embarrassed I didn't think of that. Thanks! Looks like the particular setting is likely
dot:true
Yes that's the one, no worries 👍
Reproduction:
example
.test
in the new directory with the textcoverage
inside of itnpx replace-in-file "coverage" "coverage-2" example/**
Expected: One file to be changed
Actual: No files were changed
Current workaround: Explicitly add dot files into the command
npx replace-in-file "coverage" "coverage-2" example/**,example/**/.*