Re:Yarn – A new package manager for JavaScript
by neandrake on Wednesday October 12, 2016 @12:54AM
(#12690503)
I'm not a large JS developer but with my other experiences managing dependencies, it doesn't always allow this as a possibility. A bug in your system is tracked down to the library b using [email protected] but the fix is to upgrade to b with [email protected] however a using [email protected] doesn't have an upgrade path. Waiting for another company or organization to release with an update is not an option. Our projects have several cases of requiring different versions of the same library -- we try to avoid this using the same logic you suggest but it's not a possibility in all cases so we have to work with it.
It's placing your own release cycle at the whims of your dependencies' release cycles. In the corporate world that would not be a viable solution.
It's placing your own release cycle at the whims of your dependencies' release cycles. In the corporate world that would not be a viable solution.