Closed tmchng closed 2 years ago
Thanks @tmchng, this is a valid use case but not one that I've accounted for so far. This would be a new feature and one that I'm happy to add when I next get time to work on shrinkpack.
This is still known about and will be picked up in the new codebase after #83 is released.
shrinkpack@0.19.0 has been released which adds support for npm 7 and up. This should now be working as I think this was related to the npm 5 issues.
My project has dependency structure that looks like this: MainProject --> local_module_a --> local_module_b
Directory looks like this:
MainProject/package.json:
local_module_a/package.json:
After running shrinkpack, I saw that the local_modules are packed into tarballs, with shrinkwrap entries that look like the following:
When I run npm install, I get the following error:
I then tried editing the npm-shrinkwrap.json file and change local_module's resolved path to "file: ./..." instead of tarballs, and npm install ran successfully.
The modified shrinkwrap entries:
I'm using node v6.11.0 / npm v3.10.10