-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
refactor: run scripts in parallel for build and clean #1747
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1747 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 102 102
Lines 2015 2015
Branches 454 454
=========================================
Hits 2015 2015 Continue to review full report at Codecov.
|
@@ -58,17 +59,17 @@ | |||
"clean:node": "rimraf index.js lib", | |||
"clean:es": "rimraf es", | |||
"clean:browser": "rimraf validator*.js", | |||
"clean": "npm run clean:node && npm run clean:browser && npm run clean:es", | |||
"clean": "run-p clean:*", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Isn't the same result achieved using a single &
and without having to add another dep?
"clean": "run-p clean:*", | |
"clean": "npm run clean:node & npm run clean:browser & npm run clean:es", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That doesn't work on Windows (with cmd.exe
)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Damn, shitty cmd🙃
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 🎉 ! Thank you for the PR @sachinraja
Hey, just curious, what is does the |
@sachinraja it's an internal way of organizing things between the project collaborators. The goal of the label is to let project maintainers know that this PR has already been reviewed by a collaborator and that there is no objection to it being merged. Later when enough PRs have been stacked, a maintainer will merge your PR alongside other |
Thanks @sachinraja for your PR! 🎉 |
Got it, thanks for explaining @tux-tn |
Run
build
ing for browser, node, and es in parallel. Same forclean
. This speeds up both commands.Checklist