Practical way to keep a list with the packages used directly from source?

[hypest]

We currently have some packages that we use directly from the Gutenberg submodule source, by taking advantage of Metro's smart ability to find and resolve those packages locally without them being in node_modules.

To do that we:

• have the package define the react-native entrypoint, ideally pointing to an extensionless module filename
• leave those packages out of package.json
• avoid having their source dir denylisted
• instruct Jest exactly were to find those packages
• we let Flow know where to look for the packages

It would be nice if we had a nicer way to mange this and document which packages we use directly from source.

[SergioEstevao]

@hypest is this still a thing that we need? Could it be related to the monorepo work?

[hypest]

We're not adding too many packages anymore but, this feels still relevant, to have a way to differentiate between the packages we need direct source-code access to and the rest that just appear in the package.json anyway.

Could it be related to the monorepo work?

Not sure if this issue is still relevant in the Monorepo case. @Tug , do you know if there is such a similar differentiation between some packages being accessed via direct source-level access and others that just get installed in node_modules?