Possible to run against package.json

[AutoSponge]

Here's the scenario:

I have a folder containing App. App needs a hotfix and a build but (for whatever reason) I can't simply jump branches. I need to do a clone/copy in another folder. I know the packages haven't changed, so the fastest thing to do iscp node_modules from /App to /App-hotfix. However, if have-it could read the package.json in /App-hotifx, I wouldn't need to copy.

EDIT: I think in this case I don't want to simply link the node_modules folders because I may need to add a package to enable "hotfix".

[bahmutov]

and that would be different from npm i ../<local folder> ?

[AutoSponge]

@bahmutov, If have i could run against package.json and pull the packages I need from the "sister" project folder, I could "install" much faster than npm i but npm still provides the fallback for not found cases.

If I misunderstood the purpose of have-it, I apologize. Daily, I work on a corporate network that breaks ssl to inspect EVERY dl for viruses which makes npm i on a large project something that takes quite a while.

[bahmutov]

Hmm, so we can make a "proxy" fake local package in "node_modules" that points at "sister" project, in which case it should work. This probably would need to be a command something like have <sister folder path>

for you now, what if you do npm i <sister project> --min-cache 9999999 option? that should not fetch deps again and again