๐ Introducing blaze-install: A Faster, Modern Alternative to npm for Node.js
Are you tired of waiting for npm install
to finish? Frustrated by bloated lockfiles and cryptic errors? I was tooโso I built blaze-install, a new package manager for Node.js that's all about speed, clarity, and a better developer experience.
Why blaze-install?
- Blazing Fast: Parallel downloads, extraction, and a global cache make installs 2โ10x faster than npm in real-world projects.
- Clean Lockfile: No more stale or unused dependenciesโyour lockfile is always pruned and up to date.
- Beautiful CLI: Progress bars, color, and clear, actionable error messages.
- Modern Features: Native monorepo/workspace support, automatic lockfile pruning, and a robust plugin system.
- Extensible: Add your own plugins to hook into every major lifecycle event (install, uninstall, update, audit, clean, and more).
Key Features
- ๐ Speed: Parallelized everything, with a global cache for deduplication.
- ๐๏ธ Workspaces: Native, fast monorepo support.
- ๐ Audit: Built-in security checks using the npm audit API.
- ๐งฉ Plugins: Extend blaze-install with custom hooks for every command.
- ๐งน Lockfile Pruning: No more bloatโlockfile is always clean.
- ๐ฅ Robust Error Handling: Clear, actionable feedback.
- ๐จ Beautiful Output: Progress bars and color for a modern DX.
Quick Start
npm install -g blaze-install
Then, in your project:
blaze install # Install all dependencies
blaze install <package> # Add a package
blaze uninstall <package> # Remove a package
blaze update <package> # Update a package
blaze audit # Security audit
blaze clean # Remove node_modules and cache
Plugins: Make blaze-install Your Own
Want to automate, customize, or extend your workflow? Just drop a JS file in the plugins/
directory:
// plugins/examplePlugin.js
module.exports = {
onCommand({ command, args, context }) {
console.log(`[plugin] Command executed: ${command}`);
},
beforeInstall() { /* ... */ },
afterInstall() { /* ... */ },
beforeUninstall() { /* ... */ },
afterUninstall() { /* ... */ },
beforeUpdate() { /* ... */ },
afterUpdate() { /* ... */ },
beforeAudit() { /* ... */ },
afterAudit() { /* ... */ },
beforeClean() { /* ... */ },
afterClean() { /* ... */ },
};
Why Not Just Use npm?
npm is great, but it's built for every possible use caseโincluding a lot of legacy baggage. blaze-install is focused on the modern 90%:
- Faster installs
- Cleaner lockfiles
- Better developer experience
- Extensibility for power users
blaze-install vs npm: Feature Comparison
Feature | blaze-install | npm install |
---|---|---|
Speed | ๐ Blazing fast: parallel downloads, global cache, deduplication | Slower, sequential, no global cache |
Lockfile | Always pruned, only what you need | Can become bloated, stale deps remain |
UX | Beautiful CLI, progress bars, colored output | Basic CLI, minimal feedback |
Workspaces | Native support, fast monorepo installs | Supported, but slower and more complex |
Peer/Optional Deps | Clear warnings, robust handling | Sometimes cryptic or missing warnings |
Audit | Built-in, fast, npm audit API | Built-in |
Lifecycle Scripts | Full support (preinstall, install, postinstall) | Supported |
Global Store | Yes, dedupes across projects | No |
Error Handling | Clear, actionable, modern | Sometimes cryptic |
Modern Focus | No legacy cruft, focused on 90% use case | Lots of legacy baggage |
Extensibility | Plugin system with lifecycle hooks | No plugin system |
Automatic Pruning | Yes, after uninstall/update | No |
Interactive Mode | Yes, guided menu | No |
Graph Visualization | Yes, Mermaid.js output | No |
Doctor/Repair | Yes, built-in | No |
Summary:
- blaze-install is faster, cleaner, and more extensible for modern Node.js projects.
- npm is still the default for legacy/edge-case support and ecosystem size.
Try It Out!
I'd love your feedback, bug reports, and feature requests!
Let's build a better Node.js workflow together. ๐
#node #npm #javascript #webdev #showdev
Top comments (1)
Release v1.4.0: _
Highlights: