2 ms·
> Oh that must be nice. https://prodimage.images-bn.com/pimages/9781962572439_p0_v1_s600x595.jpg https://prodimage.images-bn.com/pimages/9781962572439_p0_v1_..
by cxr 2y ago
> Oh that must be nice.
https://prodimage.images-bn.com/pimages/9781962572439_p0_v1_s600x595.jpg https://prodimage.images-bn.com/pimages/9781962572439_p0_v1_...
Just because the canonical approach at your org (or anywhere) is to use the NPM style of late-fetching dependencies to do an end-run around Git, that doesn't mean that you, personally can't take advantage of Git's branching model and its support for multiple remotes for your own, local benefit.
- davidmurdoch 2y agoHahahaha If I cared to have personal projects that still involve sitting a computer. These days I just prefer to go outside.
- cxr 2y agoI wasn't talking about hobby projects. I was talking about your personal approach to your professional work.
- davidmurdoch 2y agoInteresting, 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.