Glob arguments are not expanded on Windows

[ivkos]

• Globs are strings like *`src/.lua`** that match multiple files
• Linux bash-like shells expand them into a list of files when invoking a command, i.e. invoking this:
  • *`nodemcu-tool upload --minify --compile src/.lua`** actually executes this:
  • nodemcu-tool upload --minify --compile src/init.lua src/my_script.lua
• Windows shells (cmd.exe, PowerShell) do not do that and actually pass the arg with the wildcards into the application, so it deals with the glob internally

So, in short, the issue is that executing the same command in bash works fine, and fails in Windows shells due to the lack of glob expansion. This makes it hard to set up some useful scripts in my package.json that work on all platforms.

A possible solution would be parsing the CLI arguments and checking with is-glob whether the arg looks like a glob, then resolving it with glob into a list of files.

[AndiDittrich]

Hi @ivkos,

i can add this as features request but i didn't have the time to implement it soon - maybe in the future..

[ivkos]

Thanks Andi. I'll see if I can help with this if I find some spare time.

[AndiDittrich]

i've just added a wrapper to invoke the glob expansion for the upload command

the expansion code is still empty (passthrough)

[AndiDittrich]

v3.2.0 is out including generic glob resolver