Cannot find module kind-of

[kumavis]

encountered this problem with fresh node_modules

bundling with webpack against [email protected]

relevant issue with recent reports #4

[kumavis]

looks like [email protected] doesn't know how to parse [email protected]

WARNING in /home/xyz/Development/lavamoat/node_modules/clone-deep/utils.js 7:34-41
Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
 @ /home/xyz/Development/lavamoat/node_modules/clone-deep/index.js
 @ ../core/node_modules/merge-deep/index.js
 @ ../core/src/mergeConfig.js
 @ ./src/App.js
 @ ./src/index.js

[kumavis]

due to this lazy cache mechanism https://npmfs.com/package/clone-deep/0.2.4/utils.js#L10

[kumavis]

relevant PRs #12 #14 #9

[kumavis]

@doowb more info over here 👍

[doowb]

@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 lazy-cache.

[kumavis]

fwiw just tested the latest versions and they worked with the current merge-deep source for my basic json merging needs

• [email protected]
• [email protected]
• [email protected]

not sure what breaking changes bubble up but could always just udpate them all and cut a major 🤷

[doowb]

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 >=0.10.0, and will need to be bumped to at least what clone-deep is using (>=6) because of the use of const.

[gtsigner]

also same error invoke when using puppeteer-extra-plugin

it still dosen't work after using unlazy-loader

[kurohoan]

Can anyone help me with this problem?
I'm stuck.

[mycoin]

USE assign-deep (https://www.npmjs.com/package/assign-deep) instand !

[JasonHoku]

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'.