-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Expand globs #52
Comments
Hi @gaearon! What would you expect the output of |
The goal is to match Windows shells don't have any expansion at all. They just pass what you typed. |
Makes sense. I'd happily merge a PR to do this, or I can take a crack at it myself soon. |
Awesome! I probably won't have time to dive into it but if you can't find time either, let me know and I can create an issue in |
@gaearon I merged a fix for this and cut a 1.4.0 release. Let me know if this works for you. |
Has anything changed in 1.6.0? Cannot get globs to work:
|
Currently it seems like the program doesn't expand globs itself. This makes it impossible to run something like
source-map-explorer build/static/js/main.*
on Windows and get it to pick up a hashed filename. Which makes it hard to put intopackage.json
as one of thescripts
because the built filename is different every time.It would be great if
source-map-explorer
could expand globs (it's fine to enforce it only expands to a single file) for this particular use case on Windows.The text was updated successfully, but these errors were encountered: