📦 Offline NPM Manager - Download npm Packages Online, Install Offline

The #1 CLI tool for offline npm package management. Download npm packages when connected to the internet, then install them later — even without internet connection. Perfect for air-gapped environments, secure networks, and offline development.

A powerful command-line interface (CLI) for managing offline npm packages. Download packages with full dependency trees, cache them locally, and install in air-gapped environments without internet access.

🚀 Why Offline NPM Manager?

• ✅ Work Offline - Install npm packages without internet connection
• ✅ Air-Gapped Ready - Perfect for secure, isolated environments
• ✅ Save Bandwidth - Cache packages once, use multiple times
• ✅ Faster Installs - Local cache means instant package installation
• ✅ Dependency Management - Automatic dependency tree caching
• ✅ Cross-Platform - Works on Windows, macOS, and Linux
• ✅ Simple CLI - Easy commands: add, install, list, remove
• ✅ Production Ready - Used in enterprise offline environments

Installation

Prerequisites

• Node.js 16 or higher
• npm 8 or higher

Install Globally

npm install -g offline-npm-manager

This installs the offline-npm command globally.

uninstall Globally

npm uninstall -g offline-npm-manager

Usage

Add a Package

Download and store a package locally (requires internet):

offline-npm add <package>

Examples:

offline-npm add axios
offline-npm add react --deps
offline-npm add react@17.0.2
offline-npm add @babel/core

Options:

• -d, --deps → Download all dependencies recursively
• -s, --storage <path> → Custom storage directory

Install a Package

Install from local cache (works offline):

offline-npm install <package>

Examples:

offline-npm install axios --save
offline-npm install lodash --save-dev
offline-npm install react@17.0.2

Options:

• --save → Add to dependencies
• --save-dev → Add to devDependencies
• -s, --storage <path> → Custom storage

List Cached Packages

offline-npm list
offline-npm ls

Example output:

📦  offline-npm list

Storage: ~/.offline-npm-cache

┌──────────┬─────────┬──────────┬───────────────────────┬─────────┐
│ Package  │ Version │ Size     │ Downloaded            │ Status  │
├──────────┼─────────┼──────────┼───────────────────────┼─────────┤
│ lodash   │ 4.17.23 │ 307.5 KB │ 3/24/2026, 9:48 AM    │ ✔ ready │
│ express  │ 5.2.1   │ 22.6 KB  │ 3/24/2026, 10:15 AM   │ ✔ ready │
└──────────┴─────────┴──────────┴───────────────────────┴─────────┘

Remove a Package

offline-npm remove <package>

Example:

offline-npm remove lodash

Storage

Default locations:

• Windows → %USERPROFILE%\.offline-npm-cache
• macOS/Linux → ~/.offline-npm-cache

Override storage:

offline-npm add react --storage /custom/path

Storage Structure

~/.offline-npm-cache/
├── lodash/
│   └── 4.17.23/
│       ├── lodash-4.17.23.tgz
│       └── meta.json
├── express/
│   └── 5.2.1/
│       ├── express-5.2.1.tgz
│       └── meta.json
└── @babel/
    └── core/
        └── 7.20.5/
            ├── core-7.20.5.tgz
            └── meta.json

meta.json Example

{
  "name": "express",
  "version": "5.2.1",
  "size": 23150,
  "downloadedAt": "2026-03-24T10:15:30Z",
  "hasDeps": true
}

Uninstall

npm uninstall -g offline-npm-manager

This removes the CLI.

(Optional: manually delete cache if needed)

rm -rf ~/.offline-npm-cache

Example Workflow

# Step 1: Online
offline-npm add express@4.18.2 --deps
offline-npm add lodash
offline-npm list

# Step 2: Go Offline

# Step 3: Install
mkdir my-project && cd my-project
npm init -y

offline-npm install express@4.18.2 --save
offline-npm install lodash --save

How It Works

Requirements

• Node.js ≥ 16
• npm ≥ 8

Troubleshooting

npm not found

npm --version

Install Node.js or fix PATH.

Package not found

offline-npm add lodash

Check spelling or internet connection.

Missing dependencies

offline-npm add express --deps

💡 Use Cases

When to Use Offline NPM Manager?

🏢 Enterprise Environments

• Air-gapped development machines
• Secure networks without internet access
• Corporate firewalls blocking npm registry
• Compliance requirements for offline systems

💻 Development Scenarios

• Remote work with unreliable internet
• Traveling on planes/trains without connectivity
• Rural areas with poor internet infrastructure
• Cost savings on bandwidth-limited connections

🔒 Security & Compliance

• Isolated development environments
• Government or military systems
• Healthcare HIPAA-compliant systems
• Financial sector secure networks

🚀 Performance Optimization

• Faster CI/CD pipelines with local cache
• Reduce npm registry rate limits
• Backup critical package versions
• Test multiple package versions offline

Real-World Examples

Example 1: Air-Gapped Development

# On internet-connected machine
offline-npm add express
offline-npm add react --deps

# Copy ~/.offline-npm-cache to USB drive
# Transfer to offline machine
# Install without internet
offline-npm install express
offline-npm install react

Example 2: Team Development

# Lead developer caches packages
offline-npm add @company/ui-library
offline-npm add @company/utils

# Share cache directory on network drive
# Team members configure STORAGE_DIR
# Everyone installs from local cache

Example 3: CI/CD Pipeline

# Pre-cache dependencies in build environment
offline-npm add webpack
offline-npm add babel-core

# Build runs offline, faster and more reliable
offline-npm install webpack --save-dev

🔧 Troubleshooting

Common Issues

❌ "Package not found in cache"

# Solution: Download the package first
offline-npm add <package-name>

# Or check available packages
offline-npm list

❌ "Permission denied" errors

# Windows: Run as Administrator
# macOS/Linux: Check directory permissions
chmod -R 755 ~/.offline-npm-cache

# Or set custom storage directory
export STORAGE_DIR=/path/with/permissions

❌ "Cannot connect to npm registry"

# Check your internet connection
# Verify npm registry URL
npm config get registry

# Configure proxy if needed
npm config set proxy http://proxy.company.com:8080

❌ "Dependencies not installed"

# Always use --deps flag when adding
offline-npm add <package> --deps

# Or add dependencies manually
offline-npm add dependency-1
offline-npm add dependency-2

FAQ

Q: Can I use this without internet at all?
A: You need internet initially to download packages. After that, installations work completely offline.

Q: Does this work with private npm registries?
A: Yes! Configure your npm registry with npm config set registry <your-registry> before adding packages.

Q: How much disk space does the cache use?
A: Depends on packages cached. A typical React project might use 100-500MB. Use offline-npm list to check.

Q: Can I share the cache between multiple machines?
A: Absolutely! Copy the ~/.offline-npm-cache directory or set STORAGE_DIR to a network location.

Q: Is this compatible with yarn or pnpm?
A: The CLI works independently. You can install cached packages using standard npm commands.

Q: What happens when npm updates a package?
A: Your cached version remains unchanged. Add the package again to cache the new version.

📊 Performance Benchmarks

🌟 Keywords for Search

Search Terms: npm offline, offline npm install, npm package manager, npm cache, air-gapped npm, npm without internet, offline development tools, npm dependency cache, node package offline, npm registry mirror, cache npm packages, npm install offline, offline package manager, npm cli tool, secure npm install, enterprise npm solution, npm for disconnected environments, npm backup packages, npm version management, offline node development, npm download offline, npm offline workflow, cache npm dependencies, npm air-gapped install, npm secure environment, npm corporate firewall, npm bandwidth optimization, npm CI/CD cache, npm package backup, npm version control, npm offline development workflow

🔗 Links & Resources

• npm Package - Install from npm registry
• GitHub Repository - Source code and issues
• Report Issues - Bug reports and feature requests

📞 Support

Need help?

• 📖 Read this documentation
• 🐛 Report bugs on GitHub Issues
• 💬 Ask questions in Discussions
• 📧 Email: sagorahamed251245@gmail.com

Changelog

Version 1.0.13 (Latest)

• Added the actual repository
• Made the repository open source

Version 1.0.12

• Improved dependency resolution
• Better error messages
• Performance optimizations
• Cross-platform compatibility fixes

Version 1.0.10

• Added custom storage directory support
• Enhanced progress indicators
• Bug fixes

Version 1.0.0

• Initial release
• Core offline package management
• CLI commands: add, install, list, remove

📄 License

MIT License - See LICENSE file for details