更新私有nodejs包树的最佳（更容易/更快）方法是什么

Question

Recently I started to use a private npm packages for backend. They stored on our private packages server (an npm repository I deployed among application components.

And while I mostly like how it all works and happens, but there is a gotcha. Imagine a packages like: @example/logging , @example/utilities , @example/validation , @example/database , @example/security - low-level packages. And many of these low-level packages depends on @selfcad/logging package. @example/updates-queue , @example/subscriptions , @example/auth-tools , @example/cloud-functions and @example/backend-core packages are representing high-level abstractions and components. Each of high-level packages depending on few or sometimes all of low-level packages. Some of these packages are referenced in cloud functions via @example/cloud-functions package, especially low-level packages. Other used directly in a cloud functions. Plus there is a backend component where most of packages are used directly.

So, true headache starts, when a change must be made eg in the low-level package like @example/logging or @example/validation .

And what is the most easier way to spread the update or fix to widely referenced lower package? With nested dependencies. Like so: a package, eg @example/validation referenced directly and indirectly , like @example/configuration uses @example/validation , @example/database uses @example/validation and I updated @example/validation internals. How to spread such update across packages?

Answer 1

Maybe you should have a look to Yarn Workspaces . This is a useful feature of yarn to link dependent packages each others using a mono repo. This feature also includes auto-discovery/auto-linking.