merge-deep
merge-deep copied to clipboard
jonschlinkert
Cannot find module kind-of
encountered this problem with fresh node_modules
bundling with webpack against [email protected]
relevant issue with recent reports https://github.com/jonschlinkert/merge-deep/issues/4
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
due to this lazy cache mechanism https://npmfs.com/package/clone-deep/0.2.4/utils.js#L10
relevant PRs https://github.com/jonschlinkert/merge-deep/pull/12 https://github.com/jonschlinkert/merge-deep/pull/14 https://github.com/jonschlinkert/merge-deep/pull/9
@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.
fwiw just tested the latest versions and they worked with the current merge-deep source for my basic json merging needs
not sure what breaking changes bubble up but could always just udpate them all and cut a major :shrug:
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.
also same error invoke when using puppeteer-extra-plugin
it still dosen't work after using unlazy-loader
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'.
