4 reasons to avoid using `npm link`

• link

  1 165 6.1 TypeScript

  🔗 A better `npm link` (by privatenumber)

npx link doesn't globally install the linked package or its binaries. It doesn't remove previous links. And it works across different versions of Node.js because it makes direct symlinks. It also has a clear fail-state when it can't resolve the package path.

• nvm

  313 75,557 7.8 Shell

  Node Version Manager - POSIX-compliant bash script to manage multiple active node.js versions

  

Global install can also override existing binaries depending on your PATH configuration—the variable of paths the shell uses to lookup commands from. If you're using nvm, your configuration is likely susceptible to this.

• SurveyJS

  surveyjs.io sponsored

  Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

  

• rimraf

  16 5,484 5.8 TypeScript

  A `rm -rf` util for nodejs

Many packages on npm are designed to make changes to the file-system, such as rimraf or a code linter. In an accident, the consequences of running file-system altering code can be detrimental.

Suggest a related project