Скачать или смотреть How to Use npm for Local Package Installation in Your Projects

Discover the essential steps to install only the packages you need for your project using `npm`, without relying on a global installation or `package.json` file.
---
This video is based on the question https://stackoverflow.com/q/67861632/ asked by the user 'MagTun' ( https://stackoverflow.com/u/3154274/ ) and on the answer https://stackoverflow.com/a/67866369/ provided by the user 'MagTun' ( https://stackoverflow.com/u/3154274/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Using npm to only install the packages needed in current project

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Using npm to Install Only the Necessary Packages for Your Project

As a newcomer to Node.js and npm, you might face challenges with package installation. A common issue encountered by many developers is figuring out how to manage package installations effectively—especially when it comes to installing required packages locally, without relying on the global scope or a package.json file.

In this guide, we will dive into the solution for installing only the packages needed for your project, sharing insights into npm's behavior that can help ease your development journey.

The Challenge

You're working on a Node.js project and want to ensure that your dependencies are contained within a specific folder. You aim to do this without relying on the standard package.json setup, leading to several questions about how npm handles package directories and loading local modules.

Here are the main problems you might encounter:

Locating the correct path for installing packages.

Loading those packages within your Node application efficiently.

Your Attempted Approach

You thought of using the command:

[[See Video to Reveal this Text or Code Snippet]]

This command aims to direct npm to install packages in your desired path, rather than the standard global location. However, you ran into an impediment when it came time to require those packages in your Node application, as you received the error:

[[See Video to Reveal this Text or Code Snippet]]

This was disheartening and confusing, especially since using global installations worked just fine.

Understanding npm’s Behavior

Why Packages Were Still Present

One of the key revelations came when you discovered that although you weren't using a package.json, npm was still creating a package-lock.json. This file tracks the versions of your project’s dependencies and saves them, meaning that when you run npm install package-name, npm checks the package-lock.json and reinstalls any missing packages. This can lead to unexpected results if you're trying to clean up previous installations.

Renaming the .npm Directory

It became clear that simply renaming the folder indicated by npm root would not suffice. You also need to rename or delete the package-lock.json file to prevent npm from maintaining previous package associations.

A Clear Path Forward

Here are tailored steps to ensure you’re installing packages locally as intended:

Create Your Local Node Modules Directory:
Decide where you want your local packages to live, e.g., ./my_modules/node_modules.

Install Packages Locally Without a Global Reference:
Use the command:

[[See Video to Reveal this Text or Code Snippet]]

This installs the package directly into your specified folder.

Manage the package-lock.json:
If you created a package-lock.json initially, delete or rename it when making significant changes to your installation.

Require Your Packages Correctly:
When requiring your packages in your Node script, use the full path:

[[See Video to Reveal this Text or Code Snippet]]

Tips for Overcoming Common Hurdles

Check Module Paths: Always ensure that the path you’re trying to require is correct relative to your JavaScript file.

npm Cache Cleanup: If you encounter strange behavior, it might help to clean your npm cache using:

[[See Video to Reveal this Text or Code Snippet]]

Consider Using a package.json: While this guide provides a way to work without one, embracing package.json can significantly streamline your package management, save repetition, and help with dependency tracking moving forward.

Conclusion

Navigating through npm for local installations without a package.json could be daunting. However, by understanding npm's behavior and managing your pack