@giuseppeg Hello,

(notice the glob patterns are quoted so that the shell doesn't expand them).

The use of quotes is due to the fact that when using a pattern like *, the nodejs tries to resolve this by returning all the file matches from the process.cwd.

test.js

console.log(process.argv.slice(2));

you terminal

$ node test.js *

Such a script will work correctly.

node lib/cli.js "fixtures/**/*.html" -r test -a -o outFolder

In order for fast-glob to grab those files you shouldn't resolve the path to absolute - you should remove the following line

fast-glob works correctly, the problem lies in "!**/some/outFolder/**" and I'm trying to understand her

node lib/cli.js "fixtures/**/*.html" "!input-nesting" -r test -o outFolder  

transform to

node lib/cli.js "fixtures/**/*.html" "nesting" -r test -o outFolder

and try execute

zsh: event not found: input

As expected, it was all about shielding ! and of course, if you run the command as an npm script, then no escaping for ! is required
you terminal

node lib/cli.js "**/*.html" "\!input-nesting" -r test/fixtures -o outFolder  

you package.json

"build-one": "node lib/cli.js '**/*.html' !input-nesting -r test/fixtures -o outFolder",
"build-two": "node lib/cli.js '**/*.html' !**/one-io -r test/fixtures -o outFolder"

@Scrum I use bash instead of zsh and the CLI received the pattern just fine.

When quoted, "!**/some/outFolder/**" it is just a string and the shell won't expand it.

Then fast-glob will use the CLI args and find or exclude files just fine - that was the case with an older version of posthtml-cli before you changed it to resolve them to absolute paths.

What was the reason to prefix the patters with the absolute path?

What was the reason to prefix the patters with the absolute path?

For a correct resolution relative to the root directory

ah ok! I was indeed doing this in my own script and that messed things up