If lodash releases a major version that breaks any API changes that this repo relies on, consuming repos that use yarn will cause this library to break.
Could you please lock lodash to a specific version?
You will otherwise see an error message like the one below if using yarn and other dependencies that rely on lodash:
Pattern ["lodash@latest"] is trying to unpack in the same destination "~/Library/Caches/Yarn/v1/npm-lodash-4.17.5-99a92d65c0272debe8c96b6057bc8fbfa3bed511" as pattern ["lodash@^4.8.0","lodash@^4.8.0","lodash@^4.14.0","lodash@^4.8.0","lodash@^4.0.0","lodash@^4.13.1","lodash@^4.14.0","lodash@^4.17.4","lodash@^4.17.4","lodash@^4.11.1","lodash@^4.17.4","lodash@^4.6.0","lodash@^4.17.4","lodash@^4.17.4","lodash@^4.17.4","lodash@^4.17.4","lodash@^4.17.4","lodash@^4.17.4","lodash@^4.17.4","lodash@^4.17.4","lodash@^4.17.4","lodash@^4.17.4","lodash@^4.2.0","lodash@^4.2.0","lodash@^4.17.4","lodash@^4.17.4","lodash@^4.17.4","lodash@^4.17.4","lodash@^4.3.0","lodash@^4.17.4","lodash@^4.15.0","lodash@^4.2.0","lodash@^4.2.0","lodash@^4.2.0","lodash@^4.2.0","lodash@^4.2.0","lodash@^4.14.2","lodash@^4.17.5","lodash@^4.13.1","lodash@^4.8.0","lodash@^4.11.1","lodash@^4.17.4","lodash@^4.17.4"]. This could result in non-deterministic behavior, skipping.
If lodash releases a major version that breaks any API changes that this repo relies on, consuming repos that use yarn will cause this library to break.
Could you please lock lodash to a specific version?
You will otherwise see an error message like the one below if using yarn and other dependencies that rely on lodash: