#Firefox web extensions differences zip file#
#Firefox web extensions differences android#
#Firefox web extensions differences code#
#Firefox web extensions differences license#

Specify a particular version of Firefox Desktop to run the extension in. Use the web console when debugging content-scripts. Note: The browser console may not show all debugging output from content-scripts. Example: web-ext run -browser-consoleĮnvironment variable: $WEB_EXT_BROWSER_CONSOLE=true This opens a Browser Console on startup, so you can see log messages for your extension. This flag forces web-ext to automatically remove these discovered artifacts.Įnvironment variable: $WEB_EXT_ADB_REMOVE_OLD_ARTIFACTS -browser-console, -bc Starting from v5.0.0, web-ext run will automatically detect and warn the user if old artifacts have been found on the adb device, but it does not automatically remove them by default. This may fail, for example when the device is disconnected before Web-ext automatically removes all the temporary files that were written to the target adb device when it does exit. This will be discovered automatically by default.Įnvironment variable: $WEB_EXT_ADB_PORT -adb-remove-old-artifacts

#Firefox web extensions differences android#

Network port to use when connecting to an Android device with ADB (Android Device Bridge). This will be discovered automatically by default.Įnvironment variable: $WEB_EXT_ADB_HOST -adb-port Host name to use when connecting to an Android device with ADB (Android Device Bridge). If you don't see a list of connected devices, make sure yours is set up for development.Įxample: web-ext run -target =firefox-android -android-device FA4AX0201736Įnvironment variable: $WEB_EXT_ADB_DEVICE -adb-host If you do not specify this option, web-ext will list the IDs of each device connected.

By default, the adb executable will be located on your PATH.Įnvironment variable: $WEB_EXT_ADB_BIN -adb-device, -android-device Path to the ADB (Android Device Bridge) executable on the machine you are running web-ext from. By default, watches extension source files and reload the extension in each target as files change. Treat warnings as errors by exiting non-zero for warnings.Įnvironment variable: $WEB_EXT_WARNINGS_AS_ERRORS=true web-ext runīuilds and then temporarily installs an extension on the target application, so it can be tested. This only applies when -output is set to json.Įnvironment variable: $WEB_EXT_PRETTY=true -self-hostedĭeclares that your extension will be self-hosted. This disables messages related to hosting on .Įnvironment variable: $WEB_EXT_SELF_HOSTED=true -boringĭisables colorful shell characters so that the output only contains plain text.Įnvironment variable: $WEB_EXT_BORING=true -warnings-as-errors, -w Output only metadata about the extension in JSON.Įnvironment variable: $WEB_EXT_METADATA=true -prettyįormat the JSON output so that it's easier to read. Choices: json or text.Įnvironment variable: $WEB_EXT_OUTPUT -metadata The type of output to generate when reporting on errors.

See the addons-linter project for more information about what kind of rules are used to validate extension source. When strict_min_version is set in your extension’s manifest file, lint will report on the permissions, manifest keys, and web extension APIs used that are not available in that version.

#Firefox web extensions differences code#

Reports errors in the extension manifest or other source code files. Opens the web-ext documentation in the user's default browser. Without this option, web-ext will exit in error if the destination file already exists.Įnvironment variable: $WEB_EXT_OVERWRITE_DEST=true web-ext docs Overwrite destination package file if it exists. This allows you to continuously create a package with the most up to date source code.Įnvironment variable: $WEB_EXT_AS_NEEDED=true -overwrite-dest, -o Re-build the extension anytime you edit and save a source file.

#Firefox web extensions differences zip file#

zip file is taken from the name field in the extension manifest. zip file, ignoring files that are commonly unwanted in packages, such as. Web-ext has the following commands options specific to these commands are included as subsections.

Removing your extension from distribution.

Will I ever be able to sell through AMO?.

#Firefox web extensions differences license#

Use plain language in any privacy policy or license agreement.

Select the right platforms and versions.

The add-on description can be longer, but not too long.

Focus on key features in your screenshots.

Make sure your summary is just long enough.