Interesting, I'm not sure what you have in mind. There are 4000+ dependencies, using yarn workspaces, many are patched by `yarn`, extensive code security checks

Interesting, I'm not sure what you have in mind. There are 4000+ dependencies, using yarn workspaces, many are patched by `yarn`, extensive code security checks, PRs from forks introduce additionally complexity for reviewers, and probably a host of other "problems". To be clear, the issue isn't npm/yarn, it's the sheer number of external dependencies that I loathe.