-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to resolve 'lodash/cloneDeep' import #421
Comments
Hi, |
hey, installing lodash works but it seems like this should be included in the package.json for this package then? |
Good idea. I will pass it on to our Dev team. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Not sure if this bug is caused by my setup or how module resolution works in node (it seems like this is an unclear area), so apologies if this is a false report.
But when I try to use @cloudinary/base in my Next.js project, I get an error about failing to resolve
lodash/cloneDeep
, and then indeed I see that various places import it likelodash/cloneDeep
: https://github.com/cloudinary/cloudinary-js-base/search?q=lodash%2FcloneDeepbut in the package dependencies, it is written as
lodash.cloneDeep
. Should this be switched toimport cloneDeep from 'lodash.cloneDeep';
?I monkey-patched the files locally and changing the import statements to
lodash.cloneDeep
fixed the issue. I also was able to get the package working locally by just installinglodash
to my whole project.The text was updated successfully, but these errors were encountered: