Jopi-Mono

A powerful monorepo version management tool designed to streamline package versioning across multiple projects in a single repository.

🎯 Project Goal

Jopi-Mono aims to simplify version management in monorepo environments by providing:

• Centralized version control across all packages
• Automated dependency synchronization
• Consistent release workflows
• Cross-package dependency tracking

🚀 What You Can Do

Version Management

• Unified Versioning: Manage versions across all packages from a single point
• Dependency Tracking: Automatically track and update inter-package dependencies
• Release Coordination: Coordinate releases across multiple packages simultaneously

Workspace Operations

• Package Discovery: Automatically detect and manage packages in your monorepo
• Dependency Resolution: Resolve complex dependency graphs between packages
• Build Orchestration: Coordinate builds across dependent packages

📖 How to Use

Installation

Requirements

• Bun 1.2+ (recommended) or Node.js 18+
• Git 2.30+
• A monorepo using workspaces (npm, pnpm, Yarn, or Bun)

Install with Bun (recommended):

bun install jopi-mono --global

Or run directly with Bunx (no install needed):

bunx jopi-mono --help

📝 Command Line Usage

See all available commands:

bunx jopi-mono --help

Get help for a specific command:

bunx jopi-mono <command> --help

Typical commands include:

• check – List packages which have changes since last publication.
• publish – Publish all the packages with have changes since last publication.
• revert – Revert package version number to the public version.
• versions – Print info about package versions.
• install – Install dependencies using bun install.
• update – Update dependencies using bun update.
• ws-add <url> – Clone a git repository into the workspace.
• ws-detach <url> – Detach a project, removing dependencies of type workspace.

📝 Example Usage

Publish all updated repo:

bunx jopi-mono publish

Publish only selected packages:

bunx jopi-mono publish jopi-mono my-second-package

Fake it, for test:

bunx jopi-mono publish --fake

List the versions of all your packages (show the public and the local version number):

bunx jopi-mono version

📝 Special options

File .jopiMonoIgnore

The file .jopiMonoIgnore allows ignoring a project inside the current directory and his subdirectory.

Option jopiMono_MustIgnoreDependencies

In the package.json file, the option jopiMono_MustIgnoreDependencies allows ignoring changing the versions for the dependencies.

Without that, the versions of the projects inside the workspace are upgraded when publishing a package to match the current workspace version.

Options jopiMono_MustForceLatestVersion

In the package.json file, the option jopiMono_MustForceLatestVersion allows forcing 'latest' as version number when publishing.

It applies to all workspace dependencies and is for special use case.

Options jopiMono_MustForceAnyVersion

In the package.json file, the option jopiMono_MustForceAnyVersion allows forcing '*' (any) as version number when publishing.

It applies to all workspace dependencies and is for special use case.

📚 License

This project is licensed under the MIT License.