I have a Firefox extension. When I change the source code, every time I have to create the zip file including the source code and then make it as a .xpi file. Can I avoid this making *.xpi file steps?
For all types of Firefox extensions you can test your extension without the need to create an .xpi file for each iteration.
WebExtensions can be directly loaded as a temporary extension from the directory containing the manifest.json file. This is done from about:debugging.
You can use web-ext run to test your extension in a temporary profile.
They can be installed as an unpacked extension (all files not in a .xpi file). In addition, you can use a Firefox extension proxy file to have your extension files located in any directory you choose, not just under the profile's extensions directory.
jpm run to test your extension without directly dealing with the .xpi file.jpm xpi. However, as an .xpi, they can be loaded as temporary extensions.jpn xpi, then manually unpacking the extension.Bootstrap/Restartless extensions can be directly loaded as a temporary extension from the directory containing the chrome.manifest and install.rdf files. This is done from about:debugging.
They can be installed as an unpacked extension (all files not in a .xpi file). In addition, you can use a Firefox extension proxy file to have your extension files located in any directory you choose, not just under the profile's extensions directory.
Overlay/Legacy/XUL based extensions can not be loaded as a temporary extension.
They can be installed as an unpacked extension (all files not in a .xpi file). In addition, you can use a Firefox extension proxy file to have your extension files located in any directory you choose, not just under the profile's extensions directory.
I would suggest you read Installing add-ons for development and Installing a Temporary Add-on which cover these issues in more detail.