Skip to content
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

chore(docs,examples,templates): quote glob run params in build command #2417

Closed
wants to merge 1 commit into from

Conversation

CanRau
Copy link
Contributor

@CanRau CanRau commented Mar 21, 2022

Just ran into mysticatea/npm-run-all#200 using Yarn 3

Quoting it "dev": "run-p 'dev:*'", like mentioned in the linked issue fixed it for me with Yarn 3 and also tested Yarn 1.22.10 and npm 8.1.0, just to make sure.

So I figured as it shouldn't break anything why not always quote it?

Ref mysticatea/npm-run-all#200


As @machour requested that I fix the conflicts in #2033 but I felt it was to much mental overhead right now to get my head around fixing the other PR 🤯 I created a new one, renaming my branch and PR and also realized that I missed run-s commands containing globs as well 🤦🏻‍♂️

@MichaelDeBoey MichaelDeBoey changed the title build: quote glob run commands in package scripts chore(docs+examples+templates): quote glob run params in build command Mar 27, 2022
@MichaelDeBoey MichaelDeBoey changed the title chore(docs+examples+templates): quote glob run params in build command chore(docs,examples,templates): quote glob run params in build command Jun 3, 2022
@MichaelDeBoey
Copy link
Member

@CanRau Changes to docs/examples/templates run against main.
Could you please rebase your branch onto latest main (and fix conflicts) & set base branch to main as well?

@MichaelDeBoey MichaelDeBoey added needs-response We need a response from the original author about this issue/PR and removed needs-response We need a response from the original author about this issue/PR labels Jun 4, 2022
@MichaelDeBoey
Copy link
Member

Closing this in favor of #3595

@MichaelDeBoey MichaelDeBoey added duplicate This issue or pull request already exists and removed needs-response We need a response from the original author about this issue/PR labels Jun 29, 2022
@CanRau
Copy link
Contributor Author

CanRau commented Jun 29, 2022

Sorry the PR/notification got lost, glad there's another one 👌

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants