FORGEBOX
  • Intro
  • Release History
    • What's New With 7.7.0
    • What's New With 7.1.0
    • What's New With 7.0.0
  • Getting Started
    • Creating a user account
  • Package Management
    • CommandBox
      • Installing Packages
        • Installation Path
        • Installation Options
        • Advanced Installation
      • Publishing Packages
      • Updating Packages
      • FORGEBOX Commands
    • FORGEBOX Web UI
    • Private Packages
  • Managing Your Account
    • User Profile
    • User Account
    • Plan & Billing
    • User Tokens
    • Personal API Tokens
  • FORGEBOX Editions
  • 🆓Community
    • Intro
    • Features
  • Pro
    • Intro
    • Features
  • 🚅Business
    • Intro
    • Roles
  • ☁️Enterprise
    • Intro
    • Storage
    • CommandBox Commands
      • List
      • Register
      • Login
      • Set Default
      • Remove
    • Usage
Powered by GitBook
On this page
  • Saving dependencies
  • Production Installation
  • Verbose Installation
  • Forced Installation

Was this helpful?

Edit on GitHub
Export as PDF
  1. Package Management
  2. CommandBox
  3. Installing Packages

Installation Options

There are several options you can use to control how a package is installed.

Saving dependencies

By default, any package you install will be saved as a dependency. To save it as a development dependency instead, use the --saveDev flag.

install testbox --saveDev

If you DON'T want the package you're installing to be saved as a dependency pass save=false or negate the save flag as --!save.

install cborm --!save

Production Installation

When you install a package, all dependencies will be installed. If you want to skip development dependencies, use the --production flag. This will also cause CommandBox to obey the package's ignore property in its box.json.

install cbvalidation --production

Verbose Installation

If you're a glutton for information, or perhaps you just want to debug what's going on, set the --verbose flag to get extra debugging information out of the install command including a list of every file that's installed.

install cbi18n --verbose

Forced Installation

If CommandBox sees the directory that it was going to install into already exists with a newer or equal version of the package inside, it will decline to install again since it would be overwriting what's already there. If you want to install anyway, use the --force flag.

install cbsoap --force
PreviousInstallation PathNextAdvanced Installation

Last updated 3 years ago

Was this helpful?