npm / statusboard Goto Github PK
View Code? Open in Web Editor NEWPublic monitor/status/health board for @npm/cli-team's maintained projects
Home Page: https://npm.github.io/statusboard
License: Other
Public monitor/status/health board for @npm/cli-team's maintained projects
Home Page: https://npm.github.io/statusboard
License: Other
funding
/ npm fund
worknpm team rm <org>:developers
work (not yet staged)@npm/cli/docs/
Write tests to bring coverage on make-fetch-happen
up to 100% โ
Fix the url reference in badges
npm-registry-fetch
up to 100% โ
cli
) to write a benchmark suite for (ex. pacote
)benchmarks
work)benchmarks
npm i
"nag" at the end of output23 packages are looking for funding. Run "npm fund" to find out more.
--no-fund
flag to opt-out of the "nag" when installingnpm fund
subcommand which lists out all the funding references--no-fund
& the npm fund
subcommandpackage.json
(can use/reference this spec once updated)funding
field/value on package pagesfunding
to Pakument/Corgi objects: https://github.com/npm/validate-and-storenpm fund <package>
command._extends: ...
alone doesn't pull the config from another project's .github/settings.yml
In order to better promote adoption of 2FA among package publishers we could add a catchy-looking warning message that gets printed to the user upon every publish (if that user has disabled 2FA publish). Some other optional ideas:
https://www.npmjs.com/settings/<username>/tokens/create
benchmark/
folder with script to run benchmarking commands [R]
node_modules/
[R]results.yml
file [R][R]: required
[S]: stretch goal
scenarios.js
[DOCS]The information about order is incorrect. The ordering doesn't matter as the result of each run is a full cache, full node_modules, and full lockfile. Each next scenario begins with "everything", and must remove the things it doesn't need to complete itself.
delay
function [CHORE]Was used for testing
index.js
[DOCS]; remove commented code [CHORE]Description of what a "scenario" is would be helpful for adding new scenarios in the future. Commented code was a previous iteration and can be removed.
index.js
; write this object into a yaml file in benchmarks/results
[FEAT]Currently just writing the results to stdout. We need to keep track of the results for comparison between releases.
Currently the workflow runs on
push
which is everything: branches and pull-requests. Need to narrow scope to just pull-requests so that we can be sure to be able to write the results to a comment on said pull-request.
results.yml
" into a comment on a pull-request [FEAT]Using
actions/...@v1
should be able to write a comment for the pull-request this action ran for.
results.yml
" and committing it to the repository [FEAT]A final "
results.yml
" file should be generated at release time, the "released commit" has an idea of it's benchmark.
We want to avoid spamming pull-requests with all the results from each commit pushed to a branch with a pull-request. We should update the same comment; if a comment exists, other write a new comment.
benchmarks/results
Need to handle the edge case where that file doesn't exist.
pnpm forked repository which has ci update to commit results to repo upon merge into
master
branch
pull-request to add ci workflow for pull-request events, and pushes to
latest
,release-next
branches
pull-request for benchmarking work into the
npm/benchmark
repo
"author": "npm Inc. <[email protected]>"
"license": "MIT"
or "license": "ISC"
There are some repositories that have a
package.json
with an author set who was a previous employee. This should be changed to the above.
make-fetch-happen
etc.)Curerntly npm publish
just works but mistakes can happen and people don't wall know about --dry-run
which adds some additional details without publishing. It would be great if npm publish
had a gated [N/y]
input, and would also display the output of --dry-run
by default. This would allow the user to inspect before publishing. A --yes
flag should be added to allow ci to continue to function correctly.
master
/develop
branch in all projectslatest
branch./kv-store.js
.github
issue template from npm/cli
preview.npmjs.com
)support.npmjs.com
Zendesk help portal (ask about timelines/release schedule)We need a new kind of issue template which should capture registry related outages/issues so that we can properly clean-up/triage those in a sane manor. Messaging within this template should direct user's to our contact form (ie. https://www.npmjs.com/support) first-and-foremost as it is the more sophisticated/streamlined support vector for these types of issues.
Running make test-npm
in node is currently failing. From a quick glance I'm able to recognize that most of these errors are related to recent changes (such as adding snapshot tests but not the snapshots itself, etc).
make-fetch-happen
& publish 5.0.2
cli
make-fetch-happen
dependenciesWhen we re-open the cli/issues
on Tuesday, November 5th, we'd like to automatically generate tickets referencing any remaining #bug threads.
.sql
has been saved to Dropbox as of Sunday Nov 3rd)cli
referencing their archived counterparts discussions & labeling where possible/appropriateWhat / Why
n/a
npm
org.github/mergable.yml
file based on these config optionsn/a
At a glance would be nice to see if the repository is using travis, appvoyer, or github actions. More specifically what matrix of builds it's running.
Should be displayed in a column on the status board.
Only the build status of the "default" branch is shown. No information about the repositories build matrixes are present.
Pulling the files content from a repository should be able to find at a top level if the .travis.yml
or .appvoyer.yml
or .github/workflow/
files exist. Travis and Appvoyer would be the easiest of the files to parse, you can just look for os:
and nodejs
versions, to determine the build matrix. The github actions will be a little more work. We'll have to find the on:
field and look for push
or pull_request
for the "default" branch and review the strategy
of that to determine the build matrix.
[
"https://github.com/npm/npm-lylog",
"https://github.com/npm/package-audit",
"https://github.com/npm/redsess",
"https://github.com/npm/fastly-audit-purge",
"https://github.com/npm/node-github-url-from-git",
"https://github.com/npm/npm-fastly-purge",
"https://github.com/npm/ansible-bashpocalypse",
"https://github.com/npm/npm_conf",
"https://github.com/npm/ec2tail",
"https://github.com/npm/npm-skim-registry",
"https://github.com/npm/npm-tutor",
"https://github.com/npm/npm-registry-readme-trim",
"https://github.com/npm/registry-cert-verification",
"https://github.com/npm/npm-collection-staff-picks",
"https://github.com/npm/lylog",
"https://github.com/npm/normalize-license-data",
"https://github.com/npm/rderby",
"https://github.com/npm/shirts",
"https://github.com/npm/git-repo-manager",
"https://github.com/npm/css",
"https://github.com/npm/npm-logbot",
"https://github.com/npm/callback-tracker",
"https://github.com/npm/couch-readonly-replica",
"https://github.com/npm/keyword-context",
"https://github.com/npm/npm-fullfat-registry",
"https://github.com/npm/pingme",
"https://github.com/npm/graphics",
"https://github.com/npm/create-test-package",
"https://github.com/npm/npme-trusty",
"https://github.com/npm/npme-unknown",
"https://github.com/npm/site-structure",
"https://github.com/npm/oss-license-name-to-url",
"https://github.com/npm/ansible-ftools",
"https://github.com/npm/npme-centos65",
"https://github.com/npm/readdir-scoped-modules",
"https://github.com/npm/npme-ansible-module",
"https://github.com/npm/Paquetes-de-Codigo-Abierto",
"https://github.com/npm/uid-number",
"https://github.com/npm/npmo-auth-ldap",
"https://github.com/npm/scope-it",
"https://github.com/npm/numbat-analyzer",
"https://github.com/npm/npm-marketing-changes-feed",
"https://github.com/npm/Paquetes-de-Codigo-Abierto",
"https://github.com/npm/npmconf",
"https://github.com/npm/newww-tests",
"https://github.com/npm/talk-proposals",
"https://github.com/npm/oss-weekly",
"https://github.com/npm/npm-marketing-sidebar-blob",
"https://github.com/npm/blankie",
"https://github.com/npm/eloqua-client",
"https://github.com/npm/divot",
"https://github.com/npm/npmo-auth-sso",
"https://github.com/npm/tarball-url-info",
"https://github.com/npm/token-facilitator",
"https://github.com/npm/node-oauth2-server",
"https://github.com/npm/express-oauth-server",
"https://github.com/npm/handlebars-helper-from-package",
"https://github.com/npm/npm-tips",
"https://github.com/npm/normalize-registry-metadata",
"https://github.com/npm/realize-package-specifier",
"https://github.com/npm/new-docs",
"https://github.com/npm/private-pkgs-orgs-docs",
"https://github.com/npm/publishing-pkgs-docs",
"https://github.com/npm/npme-auth-bitbucket",
"https://github.com/npm/installation-setup-docs",
"https://github.com/npm/fstream-ignore",
"https://github.com/npm/registry-docs",
"https://github.com/npm/ansible-pg-failover-config",
"https://github.com/npm/npmo-auth-token",
"https://github.com/npm/ifttt-hook-translator",
"https://github.com/npm/sign-payload",
"https://github.com/npm/marky-markdown-integration-test",
"https://github.com/npm/how-npm-works-docs",
"https://github.com/npm/readme-tester",
"https://github.com/npm/ansible-role-deploy-update-code-git",
"https://github.com/npm/captain-hook",
"https://github.com/npm/tumblr-theme",
"https://github.com/npm/support-cli",
"https://github.com/npm/external-fetch",
"https://github.com/npm/redis",
"https://github.com/npm/npm-camp",
"https://github.com/npm/nicely-placed-modification-logs",
"https://github.com/npm/ansible-pg-failover",
"https://github.com/npm/handlebars-helper-icon",
"https://github.com/npm/npm-explicit-installs",
"https://github.com/npm/npmo-docker-compose",
"https://github.com/npm/npme-vagrant",
"https://github.com/npm/couch-login",
"https://github.com/npm/using-pkgs-docs",
"https://github.com/npm/dr-frankenstyle",
"https://github.com/npm/npm-like-im-5",
"https://github.com/npm/public-api",
"https://github.com/npm/dyn-js",
"https://github.com/npm/route66",
"https://github.com/npm/kenny-logins",
"https://github.com/npm/ansible-percona",
"https://github.com/npm/pkgize",
"https://github.com/npm/marky-compare",
"https://github.com/npm/handlebars-react",
"https://github.com/npm/next.js",
"https://github.com/npm/postgresql",
"https://github.com/npm/background-refresh-cache",
"https://github.com/npm/npme-auth-oauth2",
"https://github.com/npm/annotation-api",
"https://github.com/npm/annotation-poller",
"https://github.com/npm/ansible-influxdb",
"https://github.com/npm/ansible-role-elasticsearch",
"https://github.com/npm/decorate",
"https://github.com/npm/forza",
"https://github.com/npm/fstream-npm",
"https://github.com/npm/google-container-engine",
"https://github.com/npm/hapi-stateless-notifications",
"https://github.com/npm/humans",
"https://github.com/npm/multi-fs",
"https://github.com/npm/nm",
"https://github.com/npm/npm-authify",
"https://github.com/npm/npm-docker-couchdb",
"https://github.com/npm/npm-hook-receiver",
"https://github.com/npm/npme-auth-github",
"https://github.com/npm/npme-auth-oauth2-restricted",
"https://github.com/npm/npme-installer",
"https://github.com/npm/npmi-cli",
"https://github.com/npm/nsqjs",
"https://github.com/npm/oauth2-server-pg",
"https://github.com/npm/pivotal-ui",
"https://github.com/npm/read",
"https://github.com/npm/redis-pool",
"https://github.com/npm/rust-readme-client",
"https://github.com/npm/security-holder",
"https://github.com/npm/seq-file",
"https://github.com/npm/spife-dev-logger",
"https://github.com/npm/tarpit",
"https://github.com/npm/team-info-cache",
"https://github.com/npm/weallcontribute",
"https://github.com/npm/with-fixtures"
]
The GitHub Pages builds are failing
The last published build was 11/04/2019.
Affects the https://npm.github.io/statusboard/
GitHub Pages website.
It's borked
Should deploy a new version of the page each day via the GitHub Actions workflow.
cli
) to automate the releases of"auth-and-writes"
option instead of "auth-only"
inside the "Authorization and writes" section of that page.add node v13 support
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.