Skip to main content
Version: Next

install

The install command installs Scala applications in the installation directory configured when installing cs (~/.local/share/coursier/bin by default on Linux):

$ cs install scalafmt
$ scalafmt --version
scalafmt 3.0.6

You may give a specific version number as follows:

$ cs install scalafmt:2.4.2
$ scalafmt --version
scalafmt 2.4.2

This can be used to install a specific version of Scala itself:

$ cs install scala:2.12.15 scalac:2.12.15
$ scala -version
Scala code runner version 2.12.15 -- Copyright 2002-2021, LAMP/EPFL and Lightbend, Inc.

If the installation directory is not already on your PATH, you may add it for the current session with

$ eval "$(cs install --env)" # add installation directory in PATH in the current session

The search command can help you find the application you are looking for:

$ cs search fmt
scalafmt

The update command updates installed applications if newer versions are available:

$ cs update scala

Running cs update with no argument updates all the installed applications:

$ cs update

The uninstall command allows to uninstall it:

$ cs uninstall scala
$ scala
scala: command not found

The list command allows you to view all of your currently installed applications:

$ cs list
amm 3.0.2
coursier 2.1.24
cs 2.1.24
sbt 1.11.2
sbtn 1.11.2
scala 3.7.1
scalac 3.7.1
scalafmt 3.9.6

Pass --versions=false to only print the application names.

Java Options​

One can pass Java arguments to the installed applications:

  • by prefixing Java options with -J, and / or
  • by setting the JAVA_OPTS environment variable.

For example

$ cs install scala
$ scala -J-Xmx2g -J-Dfoo=bar -J-Dvalue=123
…
scala> sys.props("foo")
val res0: String = bar
…
$ JAVA_OPTS="-Xmx2g -Dfoo=bar -Dvalue=123" scala
…
scala> sys.props("value")
val res0: String = 123
…

Both kinds of options can be mixed, like

$ JAVA_OPTS="-Xmx2g -Dfoo=bar" scala -J-Dvalue=123
…
scala> sys.props("foo")
val res0: String = bar

scala> sys.props("value")
val res1: String = 123
…

Checksums​

Pass --validate-checksums to install so that the JVM launchers it generates record the SHA-256 of the JARs they download at run time, and check these JARs before using them, whether they're already in the coursier cache or freshly downloaded:

$ cs install scalafmt --validate-checksums

See the bootstrap documentation for more details.

update and setup accept that option too. update doesn't remember that an application was installed with it: pass it again when updating, like

$ cs update --validate-checksums

Search for the application you are looking for with cs search:

$ cs search fmt
scalafmt

Update​

Update specific applications with cs update, like

$ cs update coursier

Update all installed applications at once with

$ cs update

Uninstall​

The uninstall command uninstalls applications previously installed by the install command.

Pass it the application names of applications to uninstall, like

$ cs uninstall scala scalac

It also accepts a --all option to uninstall all applications from the installation directory.

$ cs uninstall --all

The above command uninstalls cs itself as well! If you need to reinstall it, use the installation instructions again.

Note that the uninstall command only uninstalls applications previously installed by the install command, not files put in the installation directory by other means. It checks if a file was installed by the install command by looking for its metadata in it.

Note also that some applications have a different name when installed and when used and uninstalled:

$ cs install ammonite
$ amm
…
$ cs uninstall amm # ammonite is installed as "amm"

List​

The list command lists all the installed applications. By default this will list the applications in your default installation directory. However, you can explicitly provide a different directory with the --dir flag if you have your install directory in a custom location.

$ cs list --dir /myCustomDirectory

The version each application was installed at is printed alongside its name, unless --versions=false is passed. It is left out for applications whose version couldn't be inferred from their launcher.

Channels​

Application descriptors are pulled via "channels": repositories listing available applications and how they must be installed.

By default, coursier uses the Main channel, a single JSON file living in the coursier/apps repository, at https://raw.githubusercontent.com/coursier/apps/main/listings/apps.json. It can be disabled with the --default-channels=false option.

There also exists a Contrib channel, https://raw.githubusercontent.com/coursier/apps/main/listings/apps-contrib.json, which is not used by default, and can be enabled with --contrib. For example:

$ cs install --contrib proguard

Both of those are defined on GitHub, where you can see the full list of applications that they contain. Feel free to send pull requests to add applications to the Contrib channel.

Custom channels can be provided with --channel <custom-channel>. This is useful if you create your own application descriptors.

Installation directory​

Applications are installed in OS-specific directories. These respect the "XDG Base directory specification" on Linux.

The default application directory is:

  • Linux: ~/.local/share/coursier/bin
  • macOS: ~/Library/Application Support/Coursier/bin
  • Windows:

The actual installation directory is computed via:

  • the COURSIER_BIN_DIR environment variable if it's defined, else
  • the COURSIER_INSTALL_DIR environment variable if it's defined, else
  • the coursier.install.dir Java property if it's defined,
  • else, the default OS-specific directory above is used.

Note that the install, update, uninstall, and setup commands also accept a directory via --dir or --install-dir, like

$ cs install ammonite --install-dir test-install-dir
$ test-install-dir/ammonite
…

The directory passed this way takes precedence over the ones above.

One can run cs install --setup to update profile files (Linux / macOS) or user environment variables (Windows), to add the installation directory to PATH.