🚀 Lightweight monorepo build tool written in Rust
MonoX is an intelligent build tool designed specifically for monorepo projects, helping you efficiently manage multi-package project builds through dependency analysis and task scheduling optimization.
monox.toml# Install from npm (recommended)
npm install -g monox
# or
pnpm add -g monox
# or
yarn global add monox
# Build from source (requires Rust environment)
git clone https://github.com/monoxon/monox.git
cd monox
cargo build --release
# Add executable to PATH
cp target/release/monox /usr/local/bin/
Run in your monorepo project root directory:
monox init
This will create a monox.toml configuration file.
# Analyze project dependencies and build stages
monox analyze
# Analyze specific package and its dependency chain (single package analysis)
monox analyze --package @your-org/package-name
# View detailed dependency information for single package
monox analyze --package @your-org/package-name --detail --verbose
# JSON format output
monox analyze --format json
# Build all packages (in dependency order)
monox run --all --command build
# Run specific package and its dependencies
monox run @your-org/package-name --command build
# Run multiple specific packages (multi-package execution)
monox run --packages "@your-org/pkg1,@your-org/pkg2,@your-org/pkg3" --command build
# Verbose mode to show execution process
monox run --all --command build --verbose
# Execute predefined tasks
monox exec build-all
# Execute multi-package task defined in configuration
monox exec build-frontend
# Verbose mode
monox exec test-all --verbose
# Check project health status
monox check --circular --versions --outdated
# Detailed circular dependency path information
monox check --circular --detail --verbose
# JSON format output for check results
monox check --versions --format json
# Sync project dependencies to the highest version used in the project
monox fix
# Dry-run mode (no actual modifications)
monox fix --dry-run
-v, --verbose Show detailed execution process
--no-color Disable colored output
--no-progress Disable progress display
-j, --max-concurrency Set maximum concurrency
--timeout Set task timeout (seconds)
--retry Set retry count
--continue-on-failure Continue execution on failure
-C, --workspace-root Specify workspace root directory
-l, --language Set interface language (en_us, zh_cn)
analyze - Dependency Analysismonox analyze # Analyze and display build stages
monox analyze --format json # Output in JSON format
monox analyze --verbose # Show detailed dependency relationships
monox analyze --package <package-name> # Analyze specific single package and its dependency chain
monox analyze --package <package-name> --detail # Single package analysis with detailed information
monox analyze --packages "pkg1,pkg2,pkg3" # Analyze multiple specified packages and their dependencies
run - Execute Commandsmonox run <package> --command <cmd> # Run command for specific package
monox run --all --command <cmd> # Run command for all packages
monox run --packages "pkg1,pkg2" --command <cmd> # Run command for multiple specified packages
monox run --all --command build -v # Verbose mode execution
exec - Execute Predefined Tasksmonox exec <task-name> # Execute task defined in monox.toml
monox exec build-all --verbose # Execute task in verbose mode
check - Health Checkmonox check --circular # Check circular dependencies
monox check --versions # Check version conflicts
monox check --outdated # Check outdated dependencies
monox check --circular --detail # Show detailed circular paths
fix - Problem Resolutionmonox fix --versions # Fix version inconsistencies
monox fix --dry-run # Dry-run mode, no actual modifications
init - Initializemonox init # Initialize configuration file
[workspace]
root = "."
package_manager = "pnpm" # pnpm | npm | yarn
ignore = [ # Directories or file patterns to exclude from scanning
"dist",
"build",
".git",
"*.tmp"
]
# Predefined tasks
[[tasks]]
name = "build-all"
pkg_name = "*"
desc = "Build all packages"
command = "build"
[[tasks]]
name = "test-system"
pkg_name = "@your-org/system"
desc = "Test system core package"
command = "test"
# Multi-package task example
[[tasks]]
name = "build-frontend"
desc = "Build frontend related packages"
command = "build"
packages = ["@your-org/web-ui", "@your-org/mobile-app", "@your-org/shared-components"]
# Execution configuration
[execution]
max_concurrency = 4 # Maximum concurrency
task_timeout = 300 # Task timeout (seconds)
retry_count = 0 # Retry count
continue_on_failure = false # Continue on failure
# Output configuration
[output]
show_progress = true # Show progress bar
verbose = false # Verbose output
colored = true # Colored output
# Internationalization configuration
[i18n]
language = "zh_cn" # Interface language (en_us, zh_cn)
root: Working directory root path, default "."package_manager: Package manager type, supports "pnpm", "npm", "yarn"ignore: Directories or file patterns to exclude from scanning, supports glob patterns. Note: node_modules directory is always excluded by defaultname: Task name, used for monox exec <name>pkg_name: Package name, "*" means all packages (optional, can use packages instead)packages: Array of package names for multi-package operations (optional, alternative to pkg_name)desc: Task description (optional)command: Command to executeNote: Each task must specify either pkg_name or packages field.
max_concurrency: Maximum concurrent tasks, defaults to CPU core counttask_timeout: Single task timeout (seconds), default 300retry_count: Retry count on failure, default 0continue_on_failure: Whether to continue on failure, default falseshow_progress: Whether to show progress bar, default trueverbose: Whether to show verbose output, default falsecolored: Whether to use colored output, default truelanguage: Interface language, supports "en_us" (English) and "zh_cn" (Simplified Chinese)MonoX provides complete bilingual support with all user interface texts internationalized:
--language or -lmonox.toml configuration file# Use Chinese interface
monox analyze -l zh_cn
# Use English interface
monox run --all --command build --language en_us
MonoX supports precise dependency analysis for specific packages, which is particularly useful in large monorepo projects:
# Basic single package analysis
monox analyze --package @your-org/components
# Output example:
# ◇ Analysis Results
# ● Total packages: 1
# ▪ Build stages: 3
# ◦ Packages with workspace dependencies: 1
#
# ▪ Build Stages
# ─────────────────────────
# Stage 1 (1 package):
# ● @your-org/utils
#
# Stage 2 (1 package):
# ● @your-org/core
#
# Stage 3 (1 package):
# ● @your-org/components
# Detailed information mode
monox analyze --package @your-org/components --detail
# JSON format output (convenient for script processing)
monox analyze --package @your-org/components --format json
[MONOX] ⠧ ████████████░░░░░░░░ Stage 3/5
[MONOX] Processing packages: (2/5)
[MONOX] ○ package-a
[MONOX] ▸ package-b ← Running
[MONOX] ○ package-c
[MONOX] ● package-d ← Completed
[MONOX] ○ package-e
[MONOX] ▪ Starting task: build in @your-org/utils
[MONOX] ● Task build completed in @your-org/utils, took 1250ms
[MONOX] ▪ Starting task: build in @your-org/core
Project Initialization
monox init
# Edit monox.toml configuration file
Dependency Analysis
# Analyze entire workspace
monox analyze --verbose
# Analyze specific package and its dependency chain
monox analyze --package @your-org/core --detail
Health Check
monox check --circular --versions --outdated
# Ensure project is in good state
Build Execution
monox run --all --command build --verbose
# Build all packages in dependency order
Test Execution
monox exec test-all
# Execute predefined test tasks
# Analyze dependency relationships of specific package
monox analyze --package @your-org/core
# View detailed dependency information for single package
monox analyze --package @your-org/core --detail --verbose
# Output single package analysis results in JSON format
monox analyze --package @your-org/core --format json
# Analyze multiple packages (execute separately)
monox analyze --package @your-org/utils
monox analyze --package @your-org/components
# Verbose mode: view build process and progress
monox run --all --command build --verbose
# Combined usage: most complete information output
monox analyze --verbose --detail
Contributions are welcome! Please see CONTRIBUTING.md for development guidelines.
This project is licensed under the MIT License - see the LICENSE file for details.
MonoX supports efficient operations on multiple specified packages:
# Analyze multiple specific packages
monox analyze --packages "@your-org/ui-lib,@your-org/web-app,@your-org/mobile-app" --detail
# Build multiple specific packages
monox run --packages "@your-org/ui-lib,@your-org/web-app,@your-org/mobile-app" --command build
# Test multiple packages in verbose mode
monox run --packages "pkg1,pkg2,pkg3" --command test --verbose
# Parameter priority: --all > --packages > --package
monox run --all --command build # Highest priority, builds all packages
# Define multi-package task in monox.toml
[[tasks]]
name = "build-frontend"
desc = "Build all frontend related packages"
command = "build"
packages = ["@your-org/web-ui", "@your-org/mobile-app", "@your-org/shared-components"]
[[tasks]]
name = "test-backend"
desc = "Test backend services"
command = "test"
packages = ["@your-org/api-server", "@your-org/auth-service", "@your-org/database-lib"]
# Execute multi-package tasks
monox exec build-frontend
monox exec test-backend --verbose
analyze_packages() method supports simultaneous analysis of multiple packagesFAQs
Lightweight monorepo build tool written in Rust
We found that monox demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
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.
Security News
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.
Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.