- Darcy Clarke (@darcyclarke)
- Ruy Adorno (@ruyadorno)
- Claudia Hernández (@claudiahdz)
- Jordan Harband (@ljharb)
- Tierney Cyren (@bnb)
- Housekeeping
- Introduction(s)
- Code of Conduct Acknowledgement
- Outline Intentions & Desired Outcomes
- Announcements
- PR: #152 RFC: npm fund depth
- PR: #150 RFC: Add file+pack dependency protocol
- PR: #138 RFC: Add `npm-app-id` HTTP header
- PR: #129 RFC: overrides
- PR: #126 RFC: Adding types information to the Package JSON in the registry
- PR: #121 Added proposal for package version `link#[version](comment)` syntax
- PR: #117 RFC: npm workspaces - Running Commands
- PR: #18 npm audit resolve
- Added: Update implemented RFCs to be moved over
- we are moving away from the
depth
flag in a number of different commands likeoutdated
,update
and probablyls
too - the tree in fund is different from the normal tree and applying depth makes implementation more complex
- depth seems to be used often as either all tree deps or direct deps
- there should be more steps on how we prioritize the funding info on the CLI
- how do we meaningfully show information that will actually lead to people funding contributors?
npm fund
needs UX design and will be taken care of in the near future by proper designers- the things i depend the most are most times the most invicible in my project
- we have to find better ways to show the use what they should be funding
- RFC will receive feedback from the discussion
- TBD next week
- wes had some ideas on expanding this RFC
- should ping folks to move this RFC forward
- not expected to be shipped in v7 (maybe v7.1?)
- should be mindful that feature lands on LTS versions
- should ping author on status, but RFC looks good to go
- author not on call, concerns on this feature considering the workspaces work that is in place alreadys
- no news
- ruy to be collecting feedback
- there's a specific list of top-level commands supported by the RFC: https://github.com/npm/rfcs/pull/117/files#diff-828bb29c16ce81ff3a4108b6e8dab945R33
- "everything should work the same way" - discussion on how we should be able to run all commands from the workspace
- we should expand the subset of supported commands