{"id":7411,"date":"2015-02-26T11:22:36","date_gmt":"2015-02-26T19:22:36","guid":{"rendered":"http:\/\/blog.mozilla.org\/addons\/?p=7411"},"modified":"2015-02-26T11:22:36","modified_gmt":"2015-02-26T19:22:36","slug":"jpm-replaces-cfx-for-firefox-38","status":"publish","type":"post","link":"https:\/\/blog.mozilla.org\/addons\/2015\/02\/26\/jpm-replaces-cfx-for-firefox-38\/","title":{"rendered":"JPM Replaces CFX For Firefox 38"},"content":{"rendered":"

The Python based command line tool, CFX, was what we’ve used to build, run, and test add-ons which used the Add-on SDK in the past.\u00a0 Last August, we released CFX 1.17<\/a> and there are no plans to release a new version.\u00a0 We are replacing CFX with JPM<\/a> which is a NodeJS<\/a> based equivalent that works on Firefox 38 and higher and will be accepted on AMO<\/a>.<\/p>\n

For now, you can continue to use CFX as AMO will still accept those add-ons but it is recommended that you start using JPM tool as it is the only one receiving updates.<\/p>\n

Why We Switched<\/h2>\n

We\u2019ve made the new tool for a number of reasons: For one, the Python tool supported a number of features which we wanted to deprecate.\u00a0 Also, building the tool with JavaScript instead of Python so that it may eventually be used in Firefox with the WebIDE and finally we wanted to replace the old third party module system that was invented for CFX with NPM<\/a>.<\/p>\n

If you are familiar with CFX then this guide on switching to JPM should prove useful<\/a>.<\/p>\n

Advantages<\/h2>\n