Meeting Notes 2022-08-17

[kelset]

Agenda

• add more
• status update for efforts
  • Typescript & Codegen
  • debugging
  • CI & E2E
  • Metro & symlinks
• [Lorenzo] can we define an actual driver per each effort who will own it (ex. giving status updates)?
• [Lorenzo] what are we going to use for tracking? This repo? are we going to recreate this in reactwg?
  • sidequestion: do we need a dedicated Discord section/channels?
• [Aleks] Introducing Olga, who is supporting React Desktop team and will join the Devx group
• [Rob, Moti] Another pass through Metro & symlinks with Rob & Moti to ensure we understand the pain points and are addressing them with the solution we are working on

Notes

add me!

[afoxman]

Regarding Metro & Symlinks: the quick summary is that PNPM, a commonly used package manager, creates all node_modules entries as symlinks. They point to a shared package store, outside of the repo. Soon, NPM, a VERY common package manager 😉, will support "isolation mode" which is basically the same thing as PNPM. That's coming in the near future.

These are common tools in monorepo development environments, along with yarn, which doesn't have this problem (unless you count yarn link).

[motiz88]

shared package store, outside of the repo

(Emphasis mine)

I think at least for npm isolated mode this might not be the case (not sure about pnpm). The out-of-repo scenario is different and would require different solutions.

The in-repo scenario can be solved by adding the package store to watchFolders (manually or automatically). Supporting repos with gigantic package stores may require additional work (e.g. to speed up the initial crawl and watch for changes efficiently).

[afoxman]

I read the RFC and Moti is right. That makes a difference. For npm, the store is under the root node_modules in a dit named .npm.