fix(docs,examples,templates): make npm-run-all calls work when using Yarn
#3595
Conversation
|
Thank you for signing the Contributor License Agreement. Let's get this merged! 🥳 |
lensbart
changed the title
run-p with Yarn
MichaelDeBoey
changed the title
run-p with Yarnrun-p work when using Yarn
There was a problem hiding this comment.
We already had #2417 to start working on this.
Since it didn't get any response in the last 25 days, I'd rather get this one merged instead.
1 thing I want to do here too though is also update all run-s calls as well.
I also prefer using single quotes tbh, as that makes it a bit more easy on the eyes (and has a lower cognitive load as well, since you don't need to think about where you are in the script & if you have escaped all of the correctly)
MichaelDeBoey
changed the title
run-p work when using Yarnnpm-run-all calls work when using Yarn
|
@MichaelDeBoey consider it done! |
lensbart
force-pushed
the
branch
2 times, most recently
from
37fd0f9
to
d6d0014
Compare
|
@kentcdodds fixed |
|
🤖 Hello there, We just published version Thanks! |
run-p dev:*doesn’t (but probably should) work with Yarn. Thankfully, this can be fixed quite easily by wrapping the argument in quotes.(As an aside, I find single quotes a bit cleaner than escaped double quotes, but I saw that escaped quotes were already used elsewhere so I stuck to the convention.)