statusboard
statusboard copied to clipboard
Public monitor/status/health board for @npm/cli-team's maintained projects
https://github.com/npm/npm/issues/2974 - not married to this but it came up while digging through workspace/monorepo history
### Summary Many users have asked for us to support, in `npm` itself, a mechanism to facilitate the same conflict resolution for `package-lock.json` diffs similar to the features found in...
### Summary Consumers often want to know when/if a package has begun defining install scripts as a way to safeguard against unexpected changes/mutability being added into their projects. ### Exit...
### Summary There's been some confusion about `npm`'s responsibility/capabilities to sanitize `npm-debug.log`'s especially since we've previously issued a CVE for this (ref. https://github.com/npm/cli/security/advisories/GHSA-93f3-23rq-pjfp) which was/is confusing - let's clarify that....
### Summary Many people propose new features/changes to the `npm` CLI based on their own unique interpretations/understandings/motivations. ### Exit Criteria - [ ] document goals - [ ] document motivations...
### Summary The CLI should support setting the default team a user is added to when invited to an organization. Currently, this always defaults to `"developers"` but should is now...
Better document the fact that `npm-shrinkwrap.json` file is part of the list of files that are always included in the final tarball, similar to `package.json`, `readme`, etc ref: https://github.com/npm/npm-packlist/blob/main/index.js#L166-L187
We want to refactor the commands to end up in a place where we can do per-command options and subcommands. - First refactor will be to move commands into isolated...