We are planning to deprecate the use by Firefox add-ons of the techniques described in this document.
Don't use these techniques to develop new add-ons. Use WebExtensions instead.
If you maintain an add-on which uses the techniques described here, consider migrating it to use WebExtensions instead.
Add-ons developed using these techniques might not work with multiprocess Firefox (e10s), which is already the default in Firefox Nightly and Firefox Developer Edition, and will soon be the default in Beta and Release versions of Firefox. We have documentation on making your add-ons multiprocess-compatible, but it will be more future-proof for you to migrate to WebExtensions.
A wiki page containing resources, migration paths, office hours, and more, is available to help developers transition to the new technologies.
Articles listed here provide a reference for the SDK's tools:
- Enables you to test, run, and package add-ons. cfx is is no longer supported as of Firefox 44 and no longer accepted for add-on submission, jpm should now be used instead.
- cfx to jpm
- A guide to working with jpm if you're already familiar with cfx.
- Enables your add-on to log error, warning or informational messages.
- jpm is a command-line tool that enables you to test, run, and package add-ons.
- The Node-based replacement for
cfx --force-mobile. Enables you to run and test add-ons for Firefox Mobile (aka Fennec).