#### Wednesday, May 20, 2020, 2:00 PM EST
# Open RFC Meeting - Deep Dive

### Attendees

- Darcy Clarke (@darcyclarke)
- Isaac Z. Schlueter (@isaacs)
- Jordan Harband (@ljharb)
- Claudia Hernández (@claudiahdz)
- Wes Todd (@wesleytodd)
- Ruy Adorno (@ruyadorno)

### Agenda

1. **Housekeeping**
1. Introduction(s)
1. Code of Conduct Acknowledgement
1. Outline Intentions & Desired Outcomes
1. Announcements
1. Topic(s):
1. **PR**: [#135 Clarify/Outline the RFC Withdrawal Process & Amendment](https://github.com/npm/rfcs/pull/135)
1. **PR**: [#133 RFC: Remove --depth from npm outdated](https://github.com/npm/rfcs/pull/133)
1. **PR**: [#138 RFC: Add `npm-app-id` HTTP header](https://github.com/npm/rfcs/pull/138)
1. **PR**: [#144 RFC: npm diff](https://github.com/npm/rfcs/pull/144)
1. **PR**: [#146 RFC: Notification system for cli updates](https://github.com/npm/rfcs/pull/146)
1. **PR**: [#126 RFC: Adding types information to the Package JSON in the registry](https://github.com/npm/rfcs/pull/126)
1. **PR**: [#121 Added proposal for package version `link#[version]` syntax](https://github.com/npm/rfcs/pull/121)
1. **PR**: [#117 RFC: npm workspaces - Running Commands](https://github.com/npm/rfcs/pull/117)

### Notes:

#### Clarify/Outline the RFC Withdrawal Process & Amendment
- Ability to not implement something that we previously ratified
- Ratified, Wes, Ruy and Isaacs thumbs up, no objections

#### RFC: Remove --depth from npm outdated
- No objections, doesn't seem to need any amendments
- Adding a new `--all` flag on `outdated` affects all commands
- There are other cases where we might want to use the `--all` flag (ex. `npm ls`)
- `--all` is meaninfully different from other flags
- Add physical AND logical paths?
- Logical path is hard from an output point of view since there are manye entries per dep, potentially growing exponentially
- The problem of finding logical paths might be solved by different tooling other than `npm outdated`

#### RFC: Add `npm-app-id` HTTP header
- HTTP header may contain `npm-app-id` variable which may be used in third-party applications
- Provide a hook for assigning metadata to an application
- "general purpose metadata hook"
- What are the applications/risks? Applications go way beyond the audit example presented on the RFC

### RFC: npm diff
- Ability to compare two packages (local and/or in the registry)
- Similar to `git diff`
- Complementary to `npm outdated` and `npm audit`
- Thoughts on uses-cases, developer experience, etc
- Things like `name-only`, similar to git diff (only changed file names)
- Ruy doing a POC
- npm argument parsing is different from git, so matching it exactly as git does might be tricky or not possible

### RFC: Notification system for cli updates
- remove current update-notifier logic from the cli
- cli send the user-agent, specifiying the current version of the cli and the server answers back in case there is an updated
- state of the registry engineering resources makes it difficult to add new features to the registry right now

### RFC: Adding types information to the Package JSON in the registry
- main feedback is that instead of just using a binary parameter make the "types" field more explicit