|
| 1 | +# Node.js Technical Steering Committee (TSC) Meeting 2022-12-07 |
| 2 | + |
| 3 | +## Links |
| 4 | + |
| 5 | +* **Recording**: <https://youtu.be/ku1hPGBReqk> |
| 6 | +* **GitHub Issue**: <https://github.com/nodejs/TSC/issues/1317> |
| 7 | +* **Minutes Google Doc**: <https://docs.google.com/document/d/1GH2Ua8DkpTE6-zT-pMexhzJPm2UB8KZUS54r7NFfc0E/> |
| 8 | + |
| 9 | +## Present |
| 10 | + |
| 11 | +* Matteo Collina @mcollina (TSC) |
| 12 | +* Michaël Zasso @targos (TSC) |
| 13 | +* Darshan Sen @RaisinTen (TSC) |
| 14 | +* Gireesh Punathil @gireeshpunathil (TSC) |
| 15 | +* Chengzhong Wu @legendecas (TSC) |
| 16 | +* Tobias Nießen @tniessen (TSC) |
| 17 | +* Antoine du Hamel @aduh95 (TSC) |
| 18 | + |
| 19 | +## Agenda |
| 20 | + |
| 21 | +### Announcements |
| 22 | + |
| 23 | +No announcements this week. |
| 24 | + |
| 25 | +### CPC and Board Meeting Updates |
| 26 | + |
| 27 | +Board meeting on last Friday. |
| 28 | + |
| 29 | +OpenJS World will be a mini-conference within <https://events.linuxfoundation.org/open-source-summit-north-america/> on |
| 30 | +May 10th-12th in Vancouver, Canada. Collaborator Summit will happen on the days before the event. |
| 31 | + |
| 32 | +Possible collaborator summit in Bilbao 19-21st of September <https://events.linuxfoundation.org/open-source-summit-europe/> |
| 33 | + |
| 34 | +### nodejs/node |
| 35 | + |
| 36 | +* doc: change fetch from experimental to stable [#45684](https://github.com/nodejs/node/pull/45684) |
| 37 | + |
| 38 | +* Matteo: a few factors make it difficult to call undici fetch stable (<https://github.com/nodejs/undici/issues/1737>), main issue are cookies. fetch/undici/cookies don’t play well together. More issues with blobs. Expect API changes, hopefully only additions. |
| 39 | + |
| 40 | +* Michael: mention differences in documentation? Partially non-stable? |
| 41 | + |
| 42 | +* Matteo: fine by me. Cannot read cookies right now because not allowed by spec. Discussed by WinterCG. Proposal on <https://github.com/wintercg/fetch/issues/6> and open PR in fetch spec repo: <https://github.com/whatwg/fetch/pull/1346>. Fetch is ready for general usage. Calling cookies stable requires more work. |
| 43 | + |
| 44 | +* Michael: Can it be used to send authentication headers? |
| 45 | + |
| 46 | +* Matteo: Yes. |
| 47 | + |
| 48 | +* Antoine: Can we call fetch stable if Web Streams are still experimental? |
| 49 | + |
| 50 | +* Matteo: Should stabilize both at the same time. |
| 51 | + |
| 52 | +* Antoine: Are Web Streams ready to graduate to stable? |
| 53 | + |
| 54 | +* Matteo: Should discuss in issue w\.r.t. connection to Web Streams. Matteo will leave a comment in the issue and leave this on the agenda. |
| 55 | + |
| 56 | +* Michael: Web Streams in Node.js seem more stable than in some browsers. |
| 57 | + |
| 58 | +* Expose Undici's ProxyAgent and setGlobalDispatcher within Node [#43187](https://github.com/nodejs/node/issues/43187) |
| 59 | + |
| 60 | +* Matteo: undici supports a way to implement proxy agents that https.request does not offer. Could set up a proxy just using undici. The issue is asking for more of undici to be available through Node.js, especially the ProxyAgent and the API to set those agents (<https://undici.nodejs.org/#/docs/api/ProxyAgent>). It doesn’t make sense to only expose these two and not the rest of the API. System was designed so that users can just install undici and it will work with native fetch. Question remains: do we want to expose more of undici? |
| 61 | + |
| 62 | +* Michael: Is undici stable enough? |
| 63 | + |
| 64 | +* Matteo: That’s a question for @ronag. Most of undici is stable. It has three million downloads per week. |
| 65 | + |
| 66 | +* Darshan: How would it be exposed? |
| 67 | + |
| 68 | +* Matteo: Maybe node:undici or http.undici. Would need to vendor it completely. It is not a problem of bundle size but of API surface. Matteo to write a recap in the issue. Would be good for TSC to chime in. |
| 69 | + |
| 70 | +* Tobias: Is there any chance we’d ever use a non-undici implementation of fetch, in which case undici would be baggage? |
| 71 | + |
| 72 | +* Matteo: Nobody knows! We’ll see. The current way works: npm install undici. We might want to document this though. |
| 73 | + |
| 74 | +## Strategic Initiatives |
| 75 | + |
| 76 | +## Upcoming Meetings |
| 77 | + |
| 78 | +* **Node.js Project Calendar**: <https://nodejs.org/calendar> |
| 79 | + |
| 80 | +Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. |
0 commit comments