Wildcard option doesn't seem to follow README
See original GitHub issueDespite #212, it seems the wildcard option still (v7.x) doesn’t get name
right,
concurrently “npm:watch-*”
Equivalent to: concurrently -n js,css,node “npm run watch-js” “npm run watch-css” “npm run watch-node”
but gives now:
concurrently -n watch-*js,watch-*css,watch-*node "npm run watch-js" "npm run watch-css" "npm run watch-node"
Something I understood wrong or a recurring bug?
Issue Analytics
- State:
- Created a year ago
- Reactions:7
- Comments:12 (3 by maintainers)
Top Results From Across the Web
Build Azure Repos Git repositories - Azure Pipelines
A wildcard may appear anywhere in the pattern. For paths: In Azure DevOps Server 2022 and higher, including Azure DevOps Services, a wildcard...
Read more >support for wildcard paths '**' (#2620) · Issues - gitlab-runner
My problem is that I want to set the wildcard at the beginning of the path like */TEST-*.html but this does not seem...
Read more >Is there a way to use wildcards with git checkout?
Git does deal with wildcards, using fnmatch(3). See the pathspec entry in Git glossary. But to be sure that git can see the...
Read more >Git LFS - large file storage | Atlassian Git Tutorial
Git LFS is a Git extension that improves handling of large files by lazily downloading the needed versions during checkout, rather than during...
Read more >RELEASE-README - platform/external/squashfs-tools
The -keep-as-directory option can be used when only one source directory ... doesn't exist it will be created, if it does exist and...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@paescuj awesome, that was quick. Look forward to its release.
@gustavohenke I would love not to be the only one answering 😊 … But i think I could use it that way! What about then
concurrently -n * "npm:watch-*"
?