Running multiple Sencha Cmd versions

Posted on in Architect Cmd Ext JS Ext JS 6 Sencha Touch

Do you want to run multiple versions of Sencha Cmd, because you are developing Sencha Touch, Ext JS 4, 5 and 6 apps all together?

This guide will give you answers.

Multiple Cmd versions

Now the only thing here, you will need to take care of, is that you are running multiple Sencha Cmd versions, next to each other.

From the Sencha website, you can install the older versions, just in case, you are running a fresh install:

It will install Sencha Cmd on your machine.
On a Mac, the path is: ~/bin/Sencha/Cmd/ on Windows it is probably C:\sencha\cmd\.

You can maintain the Cmd versions on a Mac in the ~/.bash_profile file. On Windows it's under your environment variables. (see this guide, I wrote earlier

Running multiple Cmd versions side by side

Something else I did. What you might consider to setup as well, especially in case you are developing Sencha Touch, Ext JS 6, and / or Ext JS 4 & 5 apps all together... Is making earlier Sencha Cmd versions available on the command -line.

When I type sencha5, I run Sencha Cmd 5 commands. When I type sencha, I run the latest Cmd 6 commands. That's because I bound these to the correct paths. You can do this too. It's very easy.

First of all make sure the paths to the earlier versions are in the .bash_profile / environment vars. (which you probably already did, since I wrote it above).
Second, and the most important step, is renaming the sencha executable (located in the Cmd installation folder) to sencha5, sencha4 etc.

And that's it!


  1. S. Cebotari says on
    August 17, 2015 at 12:01 pm

    Shame on me for not figuring this out 🙂
    Very useful.

  2. jabrane says on
    December 2, 2015 at 12:05 pm

    Thank you very much for this useful tip 🙂

  3. Tadeo says on
    March 19, 2016 at 4:55 pm

    humm it does not work for me, i have multiple versión, i followed all steps, but when i run sencha4 :command not found.

  4. Tadeo says on
    March 19, 2016 at 5:07 pm

    Sorry i got it, i was using GIT Bash, not Windows CMD, with windows CMD all works great, thank you.

Post a Comment

Your email is never published nor shared.
Required fields are marked *