Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

deps "lodash.mergewith" not found

See original GitHub issue

🐛 Bug report

I’m trying to add new package with yarn add .. but I receive the following error:

yarn add v1.22.10
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/@/types/lodash.mergewith/-/lodash.mergewith-4.6.6.tgz: Request failed \"404 Not Found\"".

I have the same issue whith the package object-assign. Both packages are listed as dependencies in yarn.lock:

  "@chakra-ui/utils@1.2.0":
    version "1.2.0"
    resolved "https://registry.yarnpkg.com/@chakra-ui/utils/-/utils-1.2.0.tgz#9385950e91455ecf480eb52bca268d3a5f8c9d6d"
    integrity sha512-oMTX8BX1+MUf+iYUafFm9tNfwa3m1cqzMcE/5iQFmNcqKlZmuADnVL28Yw7jhoeouIjANaGY+f51qj9zHgDn9Q==
    dependencies:
      "@/types/lodash.mergewith" "4.6.6"
      "@/types/object-assign" "4.0.30"
      css-box-model "1.2.1"
      lodash.mergewith "4.6.2"

💥 Steps to reproduce

Install a new package using yarn add

🧐 Expected behavior

Not having this error

🌍 System information

Software	Version(s)
Chakra UI	1.3.3
Browser	Chrome
Operating System	macOS

📝 Additional information

Anybody using Chakra UI should have the same error I guess ? Any steps to correct that ? It is kind of blocking since I don’t want to remove dependencies or Chakra, but on the other side I need to be able to install new packages…

Issue Analytics

State:
Created 3 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

with-heartcommented, Mar 5, 2021

Sure. But I doubt someone else will run in the same issue as it was a really (really) dumb mistake 😅

You never know! What seems like a dumb mistake to you is just a natural part of the development process imo. We all make mistakes and run into situations that make us feel dumb, we’re only human after all 😁

I forgot to exclude yarn.lock… @types definition packages changed to @/types

Ahhhhhhhhhhh that makes sense! I was wondering what would cause that to end up as @/types.

Glad you got were able to resolve your issue!

1reaction

binajmencommented, Mar 5, 2021

No sorry it was on my end !

Top Results From Across the Web

lodash.mergewith - npm

lodash.mergewith v4.6.2. The Lodash method _.mergeWith exported as a Node.js module. Installation. Using npm: $ {sudo -H} npm i -g npm.

lodash.mergewith vulnerabilities - Snyk

version published direct vulnerabilities 4.6.2 10 Jul, 2019 0. C. 0. H. 0. M. 0. L 4.6.1 4 Feb, 2018 0. C. 1. H. 0....

cannot find module "lodash" - node.js - Stack Overflow

The first command will clean the npm cache. (just to be sure) The second command will install all (missing) dependencies of the project....

lodash.mergewith v4.6.2 Bundlephobia

Size of lodash.mergewith v4.6.2 is 9.8 kB (minified), and 3.7 kB when compressed using GZIP. Bundlephobia helps you find the performance impact of...

GHSA-jf85-cpcp-j695 - Open Source Insights

Versions of `lodash` before 4.17.12 are vulnerable to Prototype Pollution. ... or modification of an existing property that will exist on all objects....