Currently, I am faced with a dilemma while attempting to execute a JavaScript file that is accompanied by a package.json file. The issue arises during the npm install command in the folder as it fails to locate one of the dependencies.
To address this problem, I manually remove the dependency from the package.json file and proceed to download it from the specified location. Subsequently, I place it in a separate folder which allows the npm install operation to be completed successfully.
An alternative approach involves running "npm install" on the downloaded dependency folders to ensure all necessary dependencies are included.
However, this workaround results in the creation of two distinct folders each containing numerous scripts along with their respective package.json files.
In light of these developments, I am curious about the correct course of action to manage this particular scenario effectively.
Is there a method to reference the original package.json file directly from my local hard drive or the initial internet source?