Tips And Techniques for Developers to Boost Productivity with NPM

Tips And Techniques for Developers to Boost Productivity with NPM

For managing JavaScript packages in your projects, NPM, commonly referred to as Node Package Manager, is a potent tool. It simplifies the procedure for installing packages, performing updates, managing dependencies, and running scripts. The nice part is that NPM is readily available if you already have Node.js installed on your computer because it is packaged with it.

We won’t go into the fundamentals of NPM in this article because you can find that information in the official documentation. Instead, whether you’re a seasoned developer or just getting started, we’ll present a variety of useful pointers and advice that will advance your knowledge of NPM and increase your productivity.

Run Packages Instantly without Installation:

The NPM registry is a treasure trove of utility packages that go beyond what is typically required for programming. You can use the “speed-test” package, for instance, to check the speed of your internet connection, “emoj” to look for emojis directly from the terminal, and “wifi-passwords” to discover the WiFi network password you’re currently using. Using the “npx” command, you can run these utility packages straight from the command line.

Try these commands:
npx speed-test
npx emoj unicorn
npx public-ip-cli
npx wifi-password-cli
Get Package Details Effortlessly:

Are you interested in the details of an NPM package? To retrieve information like the repository URL, dependencies, and the most recent update date, use the “npm view” command.

For instance:

npm view eslint
Install NPM Packages Faster:

Normally, “npm install” would be used to add packages and their dependencies to the local “node_modules” folder. However, you can substitute “npm ci” for it for quicker installations.

npm ci

Before installing the packages, “npm ci” also automatically deletes any pre-existing “node_modules” subdirectory, conserving you significant disk space.

Reclaim Disk Space:

After using NPM packages for a while, accumulating “node_modules” directories may start to take up a sizable amount of disk space. Be at ease! All of these directories are recognized by and can be interactively deleted from your system using the immensely helpful “npkill” program.

npx npkill
Rapidly Download Git Repositories:

It is common practice to use “git clone” to download a Git repository, although doing so takes longer because it downloads the whole git history. Try the “degit” package, which only retrieves the most recent commit from the master branch without needing the complete GitHub URL, to avoid this.

npx degit username/repo
npx degit labnol/apps-script-starter
List Installed Packages:

Make a thorough list of all NPM packages that are installed globally on your system. To view only the packages installed in the current project directory, remove the “-g” argument.

npm ls --depth=0
npm ls -g
Identify and Remove Unused Dependencies:

Your ally in finding all the NPM packages listed in the “package.json” file that aren’t being used in your project is the “depcheck” command.

npx depcheck
Uninstall any unused package with:
npm uninstall <package-name>
Uncover Unused Source Files:

“unimported” can help you locate all the unnecessary dependencies and files in your TypeScript or JavaScript projects.

npx unimported
Spot Outdated Dependencies:

Use the “npm outdated” command to look for out-of-date packages to ensure that your project’s packages are up to current. The “-g” flag will show obsolete packages that are installed globally.

npm outdated
npm outdated -g
Update Package Versions Seamlessly:

To view a list of obsolete packages in your project, use the “npm outdated” command. The “ncu” command enables you to update the “package.json” file with the most recent versions of the packages that are indicated under “dependencies” and “devDependencies.”

npm outdated
npm outdated -g
ncu -u

Another choice is to update packages to the most recent versions using “npm-check” in interactive mode.

npm-check -u
Remove Extraneous Packages:

When you want to delete locally installed packages that are not listed in the “package.json” file, “npm prune” comes to the rescue. You can preview modifications before applying them by using the “–dry-run” flag.

npm prune

A similar outcome can also be obtained by deleting the “node_modules” subdirectory and running “npm ci” once more.

Detect Vulnerable Packages:

Always be on the lookout for security! You can use the “audit” tool to search for vulnerabilities in the packages mentioned in your “package.json” file’s “dependencies” and “devDependencies” sections. If necessary, add the “fix” parameter to automatically apply fixes.

npm audit
npm audit fix
Useful NPM Package Websites:
  • Bundlephobia.com: Based on your “package.json” file, determine the size (in terms of disk space) needed to install the dependencies.
  • diff.intrinsic.com: Find the files that have changed in an update by comparing two versions of an NPM package.
  • npmtrends.com: Based on the quantity of downloads, compare the relative popularity of packages across the NPM registry.

You’ll be well-equipped to optimize your development process, increase productivity, and maintain an edge in the cutthroat world of programming if you incorporate these NPM workflow tips and tactics. Coding is fun!

 

Leave a Comment