You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 in the package dependencies, it is written as lodash.cloneDeep. Should this be switched to import 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 installing lodash to my whole project.
The text was updated successfully, but these errors were encountered:
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: