Newer changes to npm-lock-v2 resolution started to fail in cases where overrides where used. Although we never had explicit support for this, the old behavior was at least not a failure.
To remediate I have just started to explicitly support these use cases, there are likely rough edges but for now this should help support some existing use cases I have found.
What this does
Newer changes to npm-lock-v2 resolution started to fail in cases where overrides where used. Although we never had explicit support for this, the old behavior was at least not a failure.
To remediate I have just started to explicitly support these use cases, there are likely rough edges but for now this should help support some existing use cases I have found.