New Research: Supply Chain Attack on Axios Pulls Malicious Dependency from npm.Details →
Socket
Book a DemoSign in
Socket

node-linker-pro

Package Overview
Dependencies
Maintainers
1
Versions
28
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

node-linker-pro

Keep node_modules out of cloud sync folders by linking them to a local cache. Cross-platform. Includes global npm setup command.

latest
Source
npmnpm
Version
0.2.8
Version published
Maintainers
1
Created
Source

node-linker-pro

npm version npm downloads License: MIT

💾 Keep node_modules out of cloud sync folders by linking them to a local cache.
Cross-platform: macOS, Linux, and Windows.
📦 One-step global command: npm setup.

Why this exists

If your projects live in cloud-synced folders like Google Drive, OneDrive, Dropbox, or iCloud, you’ve likely seen these problems:

❌ Slow syncs — node_modules can be hundreds of MBs.
❌ Wasted storage — dependencies don’t need to be backed up.
❌ CPU/bandwidth drain while coding.

✅ Save cloud storage space.
✅ Faster project syncs.
✅ No changes to your workflow.

The solution

node-linker-pro moves your node_modules to a local cache folder outside
cloud sync, then creates a link back so your project works exactly the same.

Before

/Google Drive/MyProject
  package.json
  node_modules/   ← huge folder synced to the cloud

After

/Google Drive/MyProject
  package.json
  node_modules → /Users/you/Library/Caches/node_modules_store/<hash>

ℹ️ <hash> is a unique folder name based on your project path, ensuring no conflicts between different projects.

Features

  • 💾 Save cloud storage space.
  • ⚡ Faster project syncs.
  • 🌍 Cross-platform: macOS, Linux, Windows.
  • 📦 Works with npm, Yarn, and pnpm.
  • 🔄 Auto-installs missing dependencies.
  • 🛠 No changes to your package.json.

Installation

Install globally once:

npm i -g node-linker-pro

Usage

From any project folder:

npm setup

This will:

  • Move node_modules to the cache folder.
  • Create a symlink (mac/Linux) or junction (Windows).
  • Install dependencies if the cache is empty.

If your npm version doesn’t support npm setup:

npm-setup

Cache locations

OSDefault cache path
macOS~/Library/Caches/node_modules_store
Linux~/.cache/node_modules_store
Windows%LOCALAPPDATA%\Temp\node_modules_cache

Custom path:

# mac/Linux
EXTERNAL_NODE_MODULES_DIR="/path/to/cache" npm setup
# Windows PowerShell
$env:EXTERNAL_NODE_MODULES_DIR="D:\path\to\cache"; npm setup

When to use it

✅ You keep projects in Google Drive, OneDrive, Dropbox, or iCloud.
✅ You want a cross-platform, cloud-safe workflow.
✅ You switch between multiple OSes and don’t want to re-download dependencies.

When not to use it

❌ CI/CD pipelines (use npm ci instead).
❌ Highly isolated builds requiring separate installs for security.

FAQ

Will it break my project?
No. Your tools see node_modules normally.

What if the cache is deleted?
Run npm setup again — dependencies will reinstall.

Does it require admin rights on Windows?
No, if Developer Mode is enabled. Otherwise, Windows may ask.

License

MIT — Free to use, modify, and share.

Keywords

node_modules

FAQs

Package last updated on 12 Aug 2025

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts