StrongLoop Arc and slc are no longer under active development, and will soon be deprecated. Arc's features are being included in the IBM API Connect Developer Toolkit: Please use it instead.

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


stylewidth: 250px; border: 1px solid green; border-radius: 5px; background-color: #E6E6E6; float: right; margin-left: 15px; padding: 10px; font-size: 90%;

Building an application:

  1. Install dependencies
  2. Bundle dependencies
  3. Create deploy package, either:

Committing Use the slc build command to commit builds into a Git repository provides robust tracking and storage and .  Doing this enables you to track and version product deployments.  However, committing   Doing this manually commits both build products and dependencies (node_modules) to Git, pollutes source branches, creates massive Git commits, and huge churn on development branches and repositories. 

In contrast,   using  slc build --commit commits an exact replica of current branch source and build products onto a deployment branch. After the commit, the deployment branch tip shows as a merge of the deployment and source branches. This enables you to keep a complete history of deployment builds in Git, separate from development branches.  You can push deployment branches to the same repository as the development branches if you wish.