The third file, mmpm-env.json, is a configuration file for MMPM. As before, the MagicMirror’s config.js, can be edited, but now you can also edit MagicMirror’s custom.css file.

The config editor now accesses three files. If MagicMirror or MMPM has upgrades, they’ll be shown in this dialog. Once complete, the queue will be cleared.īy clicking on the Available Upgrades (the one that looks like a download logo), you can see the upgrades you have available, and pick which packages you’d like to upgrade on the spot. In the photo below, you can see several packages are being installed. The two icons in the upper right with floating numeric values above them are the Available Upgrades and Active Processes (from left to right).įor any of the packages listed in the marketplace, your local packages, or your external packages, clicking on the description will give you more in-depth detail.Īs for the Active Processes indicator, installing, removing, or upgrading packages will be placed into a queue, and executed in the background. The dark theme is shown in all the photos below. The icon in the upper left will allow you toggle between a light and dark theme. Additionally, you’ll notice some new icons at the top. The whole color scheme and styling is updated. If you’ve used, or are currently using MMPM, you’ll notice a dramatic difference in the appearance of the web interface. There are many major enhancements included in the upcoming release including tab autocompletion for the CLI. However, truth be told, I was never very happy with how I had thrown the project together, and I will be releasing a completely revamped CLI and upgraded GUI. Some of you may have used, or are currently using my CLI and Web interface to handle the installation and maintenance of your MagicMirror modules.

I’m the creator of MMPM, the MagicMirror Package Manager.

Magic mirror forums