|
| 1 | +#### Meeting from: February 16th, 2022 |
| 2 | + |
| 3 | +# Open RFC Meeting (npm) |
| 4 | + |
| 5 | +### Attendees |
| 6 | +- Darcy Clarke (@darcyclarke) |
| 7 | +- Nathan Fritz (@fritzy) |
| 8 | +- Ruy Adorno (@ruyadorno) |
| 9 | +- Jordan Harband (@ljharb) |
| 10 | +- Owen Buckley (@thescientist13) |
| 11 | + |
| 12 | +### Previously... |
| 13 | + |
| 14 | +- [2022-02-09](https://github.com/npm/rfcs/blob/main/meetings/2022-02-09.md) |
| 15 | + |
| 16 | +### Agenda |
| 17 | + |
| 18 | +1. **Housekeeping** |
| 19 | + 1. Introduction(s) |
| 20 | + 1. [Code of Conduct Acknowledgement](https://www.npmjs.com/policies/conduct) |
| 21 | + 1. Outline Intentions & Desired Outcomes |
| 22 | + 1. Announcements |
| 23 | + - OpenJS World 2022 |
| 24 | + - https://events.linuxfoundation.org/openjs-world/ |
| 25 | + - CFP: https://events.linuxfoundation.org/openjs-world/program/cfp/ |
| 26 | + - https://2021.stateofjs.com |
| 27 | +2. **PR**: [#525 Stop storing `integrity` for git dependencies](https://github.com/npm/rfcs/pull/525) - @nlf |
| 28 | + - @ruyadorno |
| 29 | + - what if we steered users away from git dependencies in general? |
| 30 | + - maybe we throw warnings |
| 31 | + - maybe we start notifying we're deprecating |
| 32 | + - definitely on board with this idea |
| 33 | + - @ljharb |
| 34 | + - git deps should only be for development |
| 35 | + - how do file dependencies behave? we should mimic that experience |
| 36 | + - @fritzy |
| 37 | + - we should warn when we see transitive dependencies that are gi deps |
| 38 | + - @ljharb |
| 39 | + - maintainers would have to fork & publish |
| 40 | + - deprecation indicates discouragement |
| 41 | + - not sure this is a good thing in anyway |
| 42 | + - @ruyadorno |
| 43 | + - we could do this under a config value to skip git dependencies (ex. `--ignore-git-deps`) |
| 44 | + - @ljharb |
| 45 | + - Node has a Policies feature |
| 46 | + - npm could/should probably support this |
| 47 | + - Package authors' declared policies / capabilities |
| 48 | +4. **PR**: [#522 Option for npm diff to ignore cr at eol](https://github.com/npm/rfcs/pull/522) - @oBusk |
| 49 | + - @ruyadorno |
| 50 | + - we should do whatever `git diff` does/supports |
| 51 | + - lets follow the naming of the `git` flag |
| 52 | + - keep open for another week & then ratify |
| 53 | +5. **PR**: [#4260 feat(arborist)(reify): add an ability to add a hook](https://github.com/npm/cli/pull/4260) - @fritzy |
| 54 | + - @fritzy |
| 55 | + - clarify they are not the author |
| 56 | + - should be careful about what hooks we add as features |
| 57 | + - WIP RFC |
| 58 | +6. **PR**: [#519 RFC: Package Distributions](https://github.com/npm/rfcs/pull/519) - @darcyclarke |
| 59 | + - @darcyclarke |
| 60 | + - no updates yet but seeing a lot of traction in the community |
| 61 | + - @ruyadorno |
| 62 | + - are we going to open a diff PR for the "Expanding optional dependencies conditions"? |
| 63 | + - this would mean it's easier/faster to get market validation |
| 64 | + - **Actions:** |
| 65 | + - [ ] @darcyclarke Schedule a working session to review Package Distributions & Optional Dependenyc Conditionals |
| 66 | +7. **Issue**: [#438 [RRFC] Add libc fields to select optionalDependencies should be installed or skipped](https://github.com/npm/rfcs/issues/438) - @Brooooooklyn |
| 67 | + |
| 68 | +### Other Topics |
| 69 | + |
| 70 | +- @ljharb where are we with staged releases? |
| 71 | +- @bnb `npm audit license` work? |
0 commit comments