Open bcoe opened 3 years ago
This sounds like a bug. Does it occur with standard
as well, or just standardx
?
@feross I haven't tested with standard
, it didn't happen 6.x.x
of standardx
.
I can kick off tests with standard
at some point this week, if that would help debug.
Had the same problem, but was able to fix it by using \"
instead of '
around the paths in the scripts
What version of this package are you using?
7.0.0
What operating system, Node.js, and npm version?
Windows (works fine on OSX/Linux).
What happened?
I receive an exception that the following matching rules does not work on Windows:
standardx --fix '**/*.mjs' && standardx --fix '**/*.cjs' && standardx --fix './*.mjs' && standardx --fix './*.cjs'
see: https://github.com/yargs/yargs/pull/1804
If I drop the quotes around the
--fix
statements, I begin receiving the following errors:What did you expect to happen?
I would like to figure out a glob pattern that works for
.cjs
,.mjs
, in top level and nested folder, both on Windows and Linux.Are you willing to submit a pull request to fix this bug?
If I was pointed in the right direction. Seem like potentially the tokenizer should drop quotes around glob patterns.