Skip to content

Commit 95a4e27

Browse files
authored
docs: add meeting notes from 2022-04-06 call
1 parent c5214b8 commit 95a4e27

File tree

1 file changed

+111
-0
lines changed

1 file changed

+111
-0
lines changed

meetings/2022-04-06.md

Lines changed: 111 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,111 @@
1+
#### Meeting from: April 6th, 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+
- Bogi Wennerstrøm (@boginw)
11+
- Owen Buckley (@thescientist13)
12+
- Caleb Everett (@everett1992)
13+
- Gar (@wraithgar)
14+
15+
### Previously...
16+
17+
- [2022-02-23](https://github.com/npm/rfcs/blob/main/meetings/2022-02-23.md)
18+
19+
### Agenda
20+
21+
1. **Housekeeping**
22+
1. Introduction(s)
23+
1. Code of Conduct Acknowledgement
24+
1. Outline Intentions & Desired Outcomes
25+
1. Announcements
26+
- [**v9 Roadmap**](https://github.com/npm/statusboard/issues/443)
27+
28+
#### ℹ️ Updates:
29+
30+
1. **Improving Output:**
31+
- **Issue**: [#482 [RRFC] npm should use stderr for errors](https://github.com/npm/rfcs/issues/482) - @exx8
32+
- @lukekarrys wip: streaming log file, progress bar improvements, we can take out of the agenda for now
33+
2. **Respecting returned registry `resolve` fields:**
34+
- **PR**: [#486 Resolved registry overrides](https://github.com/npm/rfcs/pull/486) - @everett1992
35+
- **PR**: [#4264 implement options affecting `resolved` value in lock files.](https://github.com/npm/cli/pull/4264) - @everett1992
36+
- @fritzy `replace registry host` can be either `default` (https://registry.npmjs.org), `always` (replacing with `registry` value) or `avoid` replacing at all. ref: https://github.com/npm/pacote/pull/143
37+
- @everett1992 an important feature needed is to skip storing the custom registry value back to the lockfile (interesting usecase with rotating registries)
38+
3. **`npm copy`:**
39+
- **PR**: [#493 docs: add npm copy rfc](https://github.com/npm/rfcs/pull/493) - @everett1992
40+
- https://github.com/npm/cli/pull/4082
41+
4. **Package Distributions:**
42+
- **PR**: [#519 RFC: Package Distributions](https://github.com/npm/rfcs/pull/519) - @darcyclarke
43+
- TBD: Schedule a separate call to discuss the proposal
44+
5. **Shared Version Specifications**:
45+
- **PR**: [#528 RFC: Shared Version Specifications](https://github.com/npm/rfcs/pull/528) - @boginw
46+
- https://github.com/npm/rfcs/pull/528#issuecomment-1068424777
47+
- @darcyclarke a way to work around this is to use `overrides` to tie various semver ranges declared for a given package in the installed graph to a specific version of a package
48+
6. **Improving Workspaces:**
49+
- **Issue**: [#556 [RRFC] improving the workspaces symlinking experience](https://github.com/npm/rfcs/issues/556) - @bnb
50+
- @ruyadorno
51+
- this has been implemented for `npm version`
52+
- can now map the same functionality to other commands (like the example, `npm init`)
53+
54+
#### ⭐️ New Items:
55+
56+
#### 1. **Issue**: [#4236 BREAKING CHANGE(bin): command should not return non-existent paths](https://github.com/npm/statusboard/issues/479) - @lineus
57+
- @ljharb
58+
- many people abuse `npm bin` & have put it in their path
59+
- should be encouraged to use `npx`
60+
- @darcyclarke
61+
- this has been added to the `v9` backlog of breaking changes
62+
- @wraithgar
63+
- should we just deprecate this command? what is the use for it these days?
64+
65+
#### 2. **Issue**: [#3806 [FEATURE] run-script with workspaces should short-circuit on script error](https://github.com/npm/cli/issues/3806) - @johndiiorio
66+
- @wraithgar
67+
- this was discussed previously and was a deliberate decision when we first implemented support to workspaces
68+
- @darcyclarke
69+
- adding a `--fast-fail` or `--bail` option sounds like a reasonable decision
70+
71+
#### 3. **Issue**: [#539 [RRFC] Security: audit lockfiles for injection](https://github.com/npm/rfcs/issues/539) - @fritzy
72+
- @fritzy
73+
- arguments have been made that if someone can modify files in your repo
74+
- @darcyclarke
75+
- could shove this check in `npm doctor`
76+
77+
#### 4. **PR**: [#547 add "obey user specifier" RFC](https://github.com/npm/rfcs/pull/547) - @ljharb
78+
- @ljharb
79+
- this came up because of a breakage
80+
- `npm install =` resolves to `^`
81+
- `npm` has always behaved this way (ie. drops all prefixes & uses the `save-prefix`)
82+
- @wraithgar
83+
- this is a bug
84+
85+
#### 5. **Issue**: [#548 [RRFC] Add flag for running NPM commands in transitive dependencies](https://github.com/npm/rfcs/issues/548) - @zgriesinger
86+
- @zgriesinger
87+
- currently use lerna for this (topological order for building)
88+
- respecting dependencies and running
89+
- @darcyclarke
90+
- https://turborepo.org/docs/features/pipelines
91+
- @ljharb
92+
- current tooling do not deviate from the regular dependency graph
93+
- @wraithgar
94+
- seem weird to have these magic/special relationships when running scripts (ex. `npm test` should not, by default, run the tests of dependants)
95+
- @ruyadorno
96+
- we've tried this awhile back with `postinstall` scripts for `.reify()`
97+
- we can probably fix
98+
99+
#### 6. **Issue**: [#549 [RRFC] support different `--before` policy per package prefix/pattern](https://github.com/npm/rfcs/issues/549) - @osher
100+
101+
#### 7. **Issue**: [#559 [RRFC] expanding behavior of `--before` to support date adjustment and setting via config](https://github.com/npm/rfcs/issues/559) - @MylesBorins
102+
103+
#### 8. **Issue**: [#4558 [BUG] Cannot work on FAT32 USB drive](https://github.com/npm/cli/issues/4558) - @szatanjl
104+
105+
#### 9. **PR**: [#564 RFC: Dependency Selector Syntax & `npm query`](https://github.com/npm/rfcs/pull/564) - @darcyclarke
106+
107+
#### 10. **PR**: [#566 RFC: Command Specific Configuration](https://github.com/npm/rfcs/pull/566) - @darcyclarke
108+
109+
#### 11. **PR**: [#550 RFC: Improve signature verification](https://github.com/npm/rfcs/pull/550) - @feelepxyz
110+
111+
#### 12. **Issue**: [#546 [RRFC] Clean up file ownership story](https://github.com/npm/rfcs/issues/546) - @ruyadorno

0 commit comments

Comments
 (0)