Skip to content

Latest commit

 

History

History
104 lines (78 loc) · 4.26 KB

2024-03-06.md

File metadata and controls

104 lines (78 loc) · 4.26 KB
Raw

Node.js Technical Steering Committee (TSC) Meeting 2024-03-06

Links

Present

  • Antoine du Hamel @aduh95 (voting member)
  • Geoffrey Booth @GeoffreyBooth (voting member)
  • Gireesh Punathil @gireeshpunathil (voting member)
  • Joyee Cheung @joyeecheung (voting member)
  • Chengzhong Wu @legendecas (voting member)
  • Matteo Collina @mcollina (voting member)
  • Michael Dawson @mhdawson (voting member)
  • Moshe Atlow @MoLow (voting member)
  • Rafael Gonzaga @RafaelGSS (voting member)
  • Richard Lau @richardlau (voting member)
  • Robert Nagy @ronag (voting member)
  • Paolo Insogna @ShogunPanda (voting member)
  • Myles Borins @MylesBorins (regular member)

Agenda

Announcements

  • Antoine, Ulises nomination passed so being onboarded
  • Rafael, release 21.7.0 being promoted today
  • Paolo, any info on when the next 20.x release will go out. Richard is planning to do one following the 21.x release so that we can pull in npm fix.

CPC and Board Meeting Updates

*Extracted from tsc-agenda labeled issues and pull requests from the nodejs org prior to the meeting.

  • No update this week.

nodejs/node

  • doc: state that removing npm is a non-goal #51951

    • Ask was that we defer in depth discussion to next meeting

  • build: enable yarn and pnpm Corepack binaries by default #51886

    • Ask was that we defer in depth discussion to next meeting
    • Corepack is version manager, integrated with Node.js for a few years
      • PR to enable by default, if you have objections etc. read the context add your objections
      • Currently corepack requires a command line option to enable it, when It is enabled, symlinks are added for pnpm and yarn, when you hit those symlinks it downloads a version and runs it for you.
      • PR removes the step of disabling. Instead the symlinks would be there by default
      • Some objections
        • Don’t have enough doc, which package managers would we support, how do we decide which ones to add. Etc.
        • Don’t have agreement on goals, etc.
        • Some objections on ux perspective that npm is not supported, and npm does not support package.json that corepack uses.
        • Some discussion around devengines field that npm would be willing to implement which could be supported in both corepack and npm
          • some would like to wait until discussion work on devengines to complete before we move forward
        • objections concerns about jumper binary approach, one of the reasons why npm has opted
        • npm opted to not be included in corepack since the beginning
        • alternate proposal, could add script that downloads corepack and then yarn, versus bundling corepack
        • Rafael, next step
          • Antoine if you have objections, put them into the issue, we will discuss in meeting next week
          • narrow down the goal of corepack

  • Expose Undici's ProxyAgent and setGlobalDispatcher within Node #43187

    • Proposal to discuss in the collaborator summit
    • Matteo, requires deep dive, for 1 hour or 2 to discuss options.
    • Please join session at collab summit
    • Richard, SemVer major? Matteo yes?
    • Michael will take off agenda until after the collab summit

nodejs/nodejs.org

  • globally installing npm should not be the recommended way for Mac and Linux #6361
    • defer to next meeting

nodejs/TSC

  • CPC representatives #1504
    • Matteo volunteered no objections,, assume we have consensus

nodejs/admin

  • Events / Collaborator Summits for 2024 #814
    • Signup form is up, please sign up if you are coming in person, if not there will be a zoom link.

nodejs/next-10

  • Deep Dive: Advocacy and promotion for the project #247

Strategic Initiatives

Upcoming Meetings

Click +GoogleCalendar at the bottom right to add to your own Google calendar.