Hacker News Reader

> Deno comes with a built in deno vendor command, which fetches all of the dependencies of the current project and puts them into a subfolder, making production deployments immune to dependencies’ hosting failures.

While this is certainly nice, should third-party code be actually committed in your version control system? I always treated it like a bad idea. Adding node_modules to gitignore is second nature now.

View on HN

If you work a company with a large monorepo, you often want to vendor all third party dependencies in the tree — you don’t want the build of this massive repo to be down because one of the five package managers it depends on is down. And if there’s a single vendor folder used by all projects, you’re certain that all parts of the tree are using the same version of the external dependency.

Reply on news.ycombinator.com