Skip to content

Latest commit

 

History

History
64 lines (52 loc) · 2.91 KB

2020-06-10.md

File metadata and controls

64 lines (52 loc) · 2.91 KB

Meeting from: June 10th, 2020

Open RFC Meeting (npm)

Attendees

  • Darcy Clarke (@darcyclarke)
  • Ruy Adorno (@ruyadorno)
  • Claudia Hernández (@claudiahdz)
  • Jordan Harband (@ljharb)
  • Tierney Cyren (@bnb)

Agenda

  1. Housekeeping
    1. Introduction(s)
    2. Code of Conduct Acknowledgement
    3. Outline Intentions & Desired Outcomes
    4. Announcements
  2. PR: #152 RFC: npm fund depth
  3. PR: #150 RFC: Add file+pack dependency protocol
  4. PR: #138 RFC: Add `npm-app-id` HTTP header
  5. PR: #129 RFC: overrides
  6. PR: #126 RFC: Adding types information to the Package JSON in the registry
  7. PR: #121 Added proposal for package version `link#[version](comment)` syntax
  8. PR: #117 RFC: npm workspaces - Running Commands
  9. PR: #18 npm audit resolve
  10. Added: Update implemented RFCs to be moved over

Notes

npm fund depth

  • we are moving away from the depth flag in a number of different commands like outdated, update and probably ls 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

Add file+pack dependency protocol

  • TBD next week

Add npm-app-id HTTP header

  • wes had some ideas on expanding this RFC
  • should ping folks to move this RFC forward

overrides

  • not expected to be shipped in v7 (maybe v7.1?)
  • should be mindful that feature lands on LTS versions

Adding types information to the Package JSON in the registry

  • should ping author on status, but RFC looks good to go

Added proposal for package version link#version syntax

  • author not on call, concerns on this feature considering the workspaces work that is in place alreadys

npm workspaces - Running Commands