That's the transitive closure of their dependencies, yes. This file contains their list of direct dependencies (which is a lot smaller, but that just tells you

That's the transitive closure of their dependencies, yes. This file contains their list of direct dependencies (which is a lot smaller, but that just tells you how much of a dependency explosion you get when you use `npm` packages): https://github.com/standardnotes/desktop/blob/develop/package.json https://github.com/standardnotes/desktop/blob/develop/packag... One thing to note is the yarn.lock is probably the transitive closure of the compile-time dependencies (`devDependencies`) and run-time dependencies (`dependencies`), so it's possible that the dependencies that actually ship with the application are quite a bit smaller. For example, `webpack` is in the devDependencies, which is the build tool. So the `yarn.lock` is listing all of the dependencies both for the runtime libraries that get used, but also the dependencies for all the build tooling as well.