-
-
Notifications
You must be signed in to change notification settings - Fork 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
🛠 Repo: Replace nps
with ordinary npm scripts
#5126
Labels
area: repository tooling
concerning ease of contribution
status: accepting prs
Mocha can use your help with this one!
Comments
voxpelli
added
status: accepting prs
Mocha can use your help with this one!
area: repository tooling
concerning ease of contribution
labels
Mar 26, 2024
voxpelli
added a commit
that referenced
this issue
Mar 26, 2024
voxpelli
added a commit
that referenced
this issue
Jul 15, 2024
voxpelli
added a commit
that referenced
this issue
Jul 15, 2024
voxpelli
added a commit
that referenced
this issue
Aug 1, 2024
* ci: use `npm ci` consistently * ci: use `actions/setup-node` cache mechanism * ci: reusable workflow for DRY:er setup * ci: remove unused `delete-runs.yml` * ci: fix matrix definitions * ci: fix matrix definitions, take 2 * ci: ensure they all scripts can use `npm run` See also #5128 * ci: add node 22 to `test-node` * ci: have the coverage run always happen on `lts/*` * ci: set permissions * ci: lock down all non-github actions by hash * ci: use reusable workflow for full tests as well * ci: remove redundant activity types * ci: add one more permissions * ci: use full sha hashes for third party workflows * ci: be consistent in naming * ci: generate the coverage report using nps for now See #5126 * ci: parallelize, run local browser test right away * ci: disable saucelabs for now, too noisy
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area: repository tooling
concerning ease of contribution
status: accepting prs
Mocha can use your help with this one!
Tooling Suggestion Checklist
master
branch of the repository.faq
label, but none matched my issue.Overview
Similar to #5124, also comes from #5042 (comment), the use of
nps
makes the script running in this repository much more exotic and as such makes threshold higher for tools likeknip
as well as to human contributors who are not used tonps
.With 52 180 weekly downloads
nps
is not an established practice within the community. To make contributions easier we should replace it with ordinary npm scripts instead.Additional Info
No response
The text was updated successfully, but these errors were encountered: