search

mysticatea / npm-run-all

A CLI tool to run multiple npm-scripts in parallel or sequential.
MIT License
5.72k stars 240 forks source link

Filesystem matches are interfering with script discovery #198

Open jonathanmorley opened 3 years ago

jonathanmorley commented 3 years ago

If you have a script block like

"scripts": {
    "lint:prettier": "prettier",
    "lint": "run-p lint:*"
}

And a file beside the package.json called lint:d, then running npm lint will throw:

ERROR: Task not found: "lint:d"

This can be worked around by using "lint": "run-p lint:\\*", but I don't think that should be necessary

yads commented 3 years ago

For me you don't even need an additional file, I'm just getting a no matches lint:* found error, unless I use your \\* modifier. This seems to only happen with yarn2. Running in yarn1, it works as expected.

Robin-Hoodie commented 3 years ago

@yads You might want to take a look at #200