Last week, I attended the -->SharePoint 2018 Conference --> in Las Vegas. There were a lot of cool announcements and demos. The SharePoint team rocks!

One of the cool things that I noticed which has nothing to do with SharePoint was that a lot of presenters who showed code had a really cool command prompt that showed the node module they were in, and their Git branch status in a pretty “boat chart”.

Console showing node module version and git branching information

I had seen this many times before, but never realized how much easier it was to get a sense of what’s going on until I was watching someone else code on a big screen.

Of course, I set out to find and configure this awesome command-line on my workstation.

This article will show you how you too can install and configure this command line interface.


During ‘s awesome session, I paid close attention to the title of his command line window. It said Cmder.

I had seen Cmder before; the article Set up your SPFx development environment mentions Cmder in the Optional Tools section.

But the version of Cmder I had installed didn’t have the fancy “boat chart” at the top that got my attention.

As it turns out, you need to download another custom prompt for Cmder that adds the Powerline (that’s the real name for the “boat chart”) at the top.

Here is how to install and configure Cmder with the Powerline command prompt:

Installing Cmder

  1. Go to and download either the Mini pack or the Full pack.
  2. Unzip the package. Cmder is designed to be portable and to require no administrative privileges to run, so their instructions tell you to not install it in the Program Files folder (where you’ll need administrative privileges). I placed it in C:\Users\[myusername]\AppData\Local\cmder.
  3. Open a command prompt in Administrative mode from the folder where you copied the Cmder files
  4. From the command-prompt, type:
    cmder /REGISTER ALL
  5. If you get an Access Denied error, you probably forgot to run the command in Administrative mode. If you don’t know how to do that, type cmd from your Start menu, and right-click on Command Prompt and select Run as administrator.
  6. Cmder should be installed. You can verify by opening a new File Explorer window and right-clicking on a folder. You should get a Cmder Here option.
    Cmder Here

Unfortunately, if you open Cmder with that command line, you don’t get the fancy Powerline.

Let’s fix that!

Installing Cmder Powerline custom prompt

The custom prompt changes the Cmder prompt to include the following modifications:

  • The folder portion of the prompt is displayed in blue. The user’s home folder is also replaced with a tilde (~).
  • If the current folder is an npm package, the prompt will display the package package name and version number in teal.
  • If the current folder is a Git repository, the prompt will display the branch name with a green colour if the branch is unchanged, or yellow if changes are found.

To install the Cmder Powerline custom prompt:

  1. Download the . You can do so by clicking on each TTF file in GitHub and selecting View Raw. For your convenience, here are the links to the raw files:

  2. Once dowloaded each font, install them by double-clicking them and selecting Install on each one of them.
  3. Copy all the .lua files from the source and place them in the config folder under the Cmder install folder.
  4. If you haven’t done so yet, launch a Cmder window by going to the folder where you installed in and double-clicking on Cmder.exe 
  5. From the Cmder window, open the Settings by hitting Windows-Alt-P.
  6. From the Main settings area, select Anonymice Powerline font from the Alternative font (pseudographics, CJK, etc.) drop-down.
  7. In the Unicode ranges combo box, type E0A0-E0B0 and select Apply.
  8. Select Save settings to save your settings and return to the command prompt in Cmder.


That’s all you need to do.

Cmder with Visual Studio Code

If you want Cmder to show up in Visual Studio Code, follow these steps:

  1. Launch Visual Studio Code.
  2. From the File menu, select Preferences | Settings or use Ctrl-, (Control and comma). This will open your settings editor.
  3. In the right-pane of the settings editor (the one that’s actually editable), insert the following JSON, just before the last , making sure to replace the path to Cmder with the path where you installed it.
    "terminal.external.windowsExec": "C:\\Users\\[myusername]\\AppData\\Local\\cmder\\Cmder.exe",
    "": "cmd.exe",
    "" : [

That’s all!


I hope that you’ll find Cmder and the custom Cmder Powerline command-prompt useful in your SPFx development endeavors.

I know I did!

For More Information lists more information about Cmder, including the super-powerful shortcut keys.

is the brilliant mind behind the Cmder Powerline command-prompt.

Sahil Malik has detailed instructions (and a video!) to to integrate with Cmder Visual Studio Code.


In the previous revision of this article, I had forgotten to include the steps to copy the .lua files to the config folder. It works much better when you include all the steps, it turns out 🙂



Microsoft MVP and PnP Team Member. Independent consultant. Certified SCRUM Master. SharePoint, Office 365 and Dynamics 365 are his favourite toys.


  1. i did all the steps but i can not see any fancy powerline… also when i start cmder.exe i have this at the top c:\windows\system32 was unexpected at this time.

  2. Pingback: My GitHub cheat sheet for PnP contributions — an interactive cheat sheet – Tahoe Ninjas

  3. Pingback: Ultimate Developer Tool List for SPFx – Tahoe Ninjas

How can I help?

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: