Upgrade to The Lounge v3

This guide lists all breaking changes made between the releases of v2.7.1 and v3.0.0 that may require you taking actions before upgrading and running The Lounge.

In addition to the items listed in this guide, you may want to enable or configure new features of The Lounge v3 manually. For a more detailed list of all changes and additions, refer to the release notes and all merged pull requests for this release.

In this page:

  1. TL;DR
  2. Environment
  3. CLI
  4. Configuration file
  5. Client


  • You need Node.js v6.13.0 or more recent.
  • Everything called lounge (such as commands, directories, etc.) becomes thelounge.
  • thelounge start does not have options other than --config anymore.
  • In the configuration file, autoload and logs settings can be removed, themes and debug settings have changed.
  • In the client, we warn when using insecure IRC servers, some shortcuts have changed, and the browser support list has changed.
  • User log format has changed and may break your tools and scripts.


  • The Lounge v3.0.0 now requires Node.js v6.13.0 or more recent to run. However, we recommend using the latest Node.js v8.x, current LTS version at the time of writing this guide. Node.js v7 and v9 have reached End-of-Life and are therefore not supported.
  • The environment variable $LOUNGE_HOME that can be used to point The Lounge to a specific home directory (housing configuration file, packages, user settings, etc.) is now called $THELOUNGE_HOME. More details here.
  • In situations where The Lounge has been installed from the npmjs.com registry or from source, we now recommend using the yarn package manager in lieu of the npm. More details here.
  • User log files, located ${THELOUNGE_HOME}/logs/<user>/ by default, have changed. Server directories are now named after their name in The Lounge plus a randomized identifier to avoid duplicates (see #2366). Changes were also made to the logging format itself (see #2501). If you are using tools or scripts relying on log format, you will need to update them accordingly.
  • The Docker image has been renamed into thelounge/thelounge on DockerHub. The base image does not come with vim nor nano, and the slim flavor was removed. The default data path was changed from /home/lounge/data to /var/opt/thelounge.


  • The lounge CLI has now been renamed into thelounge.
  • The Lounge will now print a warning on the server console if CLI commands are not run under the same system user than the configuration file owner.
  • The default location of The Lounge’s home directory has changed from ~/.lounge to ~/.thelounge. If you were still relying on ~/.lounge, we recommend renaming the directory prior to running thelounge start.
  • thelounge start used to support a few options such as --host, --port, etc. A new option introduced in v2.7.0, --config (aliased -c), can be used to override any setting from the configuration file using a key=value format, applicable to all subcommands of the CLI. It effectively duplicates these options, which have now be removed. Here are the equivalent values using the new option:
    • -H, --host <ip> is now -c host=<ip>
    • -P, --port <port> is now -c port=<port>
    • -B, --bind <ip> is now -c bind=<ip>
    • --public is now -c public=true
    • --private is now -c public=false
  • The --home option has been removed. Use the $THELOUNGE_HOME environment variable instead.
  • thelounge config has been removed. To edit the configuration file, you must now open it manually using your preferred editor. As a reminder, The Lounge’s home directory is displayed as part of thelounge --help, and the actual configuration file path loaded by The Lounge is displayed when running thelounge start.

Configuration file

  • The autoload setting has had no effect since v2.2.0 as The Lounge automatically loads user configuration files on creation, edition, and deletion. The warning recommending to remove this setting from your configuration file has now been removed.
  • The debug setting has been an object since v2.2.0 to control debugging with more granularity. Available keys are ircFramework and raw. The fallback allowing you to use the previous boolean format has now been removed.
  • The theme setting has referred to a theme name since v2.5.0, while it used to be a path to the CSS file for that theme. The fallback to the previous format has now been removed. To use the theme setting, either specify themes shipped with The Lounge (default or morning) or installed from the npm registry (using the thelounge install).
  • The default theme referred to by the theme setting has been renamed from example to default. As a side note, the default theme in The Lounge v3.0.0 is now substantially different. You can restore the previous look of The Lounge by installing the theme thelounge-theme-classic. This theme is currently looking for maintainers.
  • Two themes that previously shipped with The Lounge, crypto and zenburn, have now been extracted into external themes at thelounge-theme-crypto and thelounge-theme-zenburn. If you were using them in the theme setting, you need to install them and update the setting accordingly. These themes are now looking for maintainers.
  • The logs.format and logs.timezone settings have been removed. The Lounge now logs timestamps using a format of YYYY-MM-DD HH:mm:ss (which used to be the default value) in UTC timezone.


  • IRC servers connected to an insecure connection (i.e. the TLS checkbox was not checked when filling the network connect form) now display a warning sign icon and are colored in orange in the channel list. If it is available for this network, you can change this setting by right-clicking on the network name in the channel list, click on “Edit this network…”, and update the checkbox (along with the port and sometimes the hostname) before saving the settings again. You will have to disconnect and re-connect to this server.
  • To navigate through windows in the channel list from your keyboard, you must now use alt+ / alt+ in lieu of ctrl+ / ctrl+, more often used in other chat clients.
  • We have updated our build pipeline to better reflect our browser support. The Lounge now supports browsers released less than a year ago (and Firefox ESR), while we used to support the last 2 versions of all browsers. In practice, this drops support for some of the least used browsers on mobile (QQ browser, UC browser, Android Browser, Baidu Browser, Blackberry Browser, IE Mobile, Opera Mini, and Opera Mobile), and IE 10/11 on desktop. It however gives slightly more support flexibility for earlier versions of Chrome (62+), Firefox (56+ and ESR), and Opera (48+).