|
| 1 | +#### Meeting from: November 25th, 2020 |
| 2 | + |
| 3 | +# Open RFC Meeting (npm) |
| 4 | + |
| 5 | +### Attendees |
| 6 | +- Darcy Clarke (@darcyclarke) |
| 7 | +- Christian Siebmanns (@christian24) |
| 8 | +- Ruy Adorno (@ruyadorno) |
| 9 | +- Isaac Z. Schlueter (@isaacs) |
| 10 | + |
| 11 | +### Agenda |
| 12 | + |
| 13 | +1. **Housekeeping** |
| 14 | + 1. Introduction(s) |
| 15 | + 1. [Code of Conduct Acknowledgement](https://www.npmjs.com/policies/conduct) |
| 16 | + 1. Announcements |
| 17 | +1. **Issue**: [#287 [RRFC] Add nohoist option for workspaces](https://github.com/npm/rfcs/issues/287) - @socialwyze-franklin |
| 18 | +1. **PR**: [#279 RFC for --default-command](https://github.com/npm/rfcs/pull/279) - @isaacs |
| 19 | +1. **Issue**: [#275 [RRFC] `registry:<url>:<name>[@<version-range>]` dependency specifier](https://github.com/npm/rfcs/issues/275) - @isaacs |
| 20 | +1. **PR**: [#273 RFC: npm workspaces - Config management](https://github.com/npm/rfcs/pull/273) - @ruyadorno |
| 21 | +1. **PR**: [#272 RFC: add preferDev field to package.json](https://github.com/npm/rfcs/pull/272) - @Ginden |
| 22 | +1. **PR**: [#217 RFC: add registry per package per organisation](https://github.com/npm/rfcs/pull/217) - @baloran |
| 23 | + |
| 24 | +### Notes |
| 25 | + |
| 26 | +#### **Issue**: [#287 [RRFC] Add nohoist option for workspaces](https://github.com/npm/rfcs/issues/287) - @socialwyze-franklin |
| 27 | +- Action: queue up a proper RFC and deep dive for "hoisting"/reifying "strategies" |
| 28 | + |
| 29 | +#### **PR**: [#279 RFC for --default-command](https://github.com/npm/rfcs/pull/279) - @isaacs |
| 30 | +- Reminder from last conversation: |
| 31 | + - It may be disruptive |
| 32 | + - Sharing commands might become more challenging |
| 33 | + - Make the current default help-behavior a little bit more helpful, adding a note in case there's a script with that name |
| 34 | +- Default `npm` behavior takes from the old-days of clis having the default behavior be just print help output, similar to (`curl`, `tar`, etc) |
| 35 | +- @christian24: The diff binary (e.g: `npr`) would make it so that we avoid the namespace-conflict situation |
| 36 | +- @darcyclarke: Limitting the future new subcommands we could possibly add is one of the major inconvenients |
| 37 | +- @isaacs: `npm start`, `npm stop`, `npm restart` were added very early on in the cli and might have been better to never have had it in the first place |
| 38 | +- @ruyadorno: Not necessarily onboard with the idea of adding new binaries such as `npr`, still think it's better for aliases to live in userland packages, bash profiles, etc. |
| 39 | +- @darcyclarke: builtin binaires provide a good value for the new/intermediate developers since it provides a sane default behavior with no need to tweak configs |
| 40 | + |
| 41 | +#### **Issue**: [#275 [RRFC] `registry:<url>:<name>[@<version-range>]` dependency specifier](https://github.com/npm/rfcs/issues/275) - @isaacs |
| 42 | +- @isaacs: Seems to be quite actionable and uncontrovertial, need to write down the spec now |
| 43 | + |
| 44 | +#### **PR**: [#273 RFC: npm workspaces - Config management](https://github.com/npm/rfcs/pull/273) - @ruyadorno |
| 45 | +- @ruyadorno: From last call, listing workspaces is non-controvertial and very actionable but adding/removing workspaces is still up in the air since there were concerns brought up during the last time we discussed it |
| 46 | +- @ruyadorno: We need to collect more feedback and evolve this RFC |
| 47 | + |
| 48 | +#### **PR**: [#272 RFC: add preferDev field to package.json](https://github.com/npm/rfcs/pull/272) - @Ginden |
| 49 | + |
| 50 | +#### **PR**: [#217 RFC: add registry per package per organisation](https://github.com/npm/rfcs/pull/217) - @baloran |
| 51 | +- @darcyclarke: This is the preceding PR to [#275](https://github.com/npm/rfcs/issues/275) dependency specifier. We should circle back to this once work there is done. |
0 commit comments