-
-
Notifications
You must be signed in to change notification settings - Fork 34
Cannot find module kind-of #18
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
looks like
|
due to this lazy cache mechanism https://npmfs.com/package/clone-deep/0.2.4/utils.js#L10 |
@doowb more info over here 👍 |
@kumavis :) I just saw these... thank you for more information. Have you tried unlazy-loader? It might be useful until we update the dependencies using |
fwiw just tested the latest versions and they worked with the current
not sure what breaking changes bubble up but could always just udpate them all and cut a major 🤷 |
Yes... I believe the path will be to update the dependencies and publish a new major version. Most of the breaking changes have to do with Node.js compatibility... this is currently set at |
Can anyone help me with this problem? |
USE assign-deep (https://www.npmjs.com/package/assign-deep) instand ! |
Hello! If you're using webpack and electron I found a fix for this by making sure to include any merge-deep dependencies as an external and to declare the node_modules path relative to your package.json in your package.json as an 'extraResource'. |
encountered this problem with fresh node_modules
bundling with webpack against
merge-deep@3.0.3
relevant issue with recent reports #4
The text was updated successfully, but these errors were encountered: