When runtimes have remote debugging enabled, they start a server that listens
for incoming connections. Devices connected via USB can also have their remote
debugging sockets forwarded to local TCP/IP ports by the Android Debug Bridge
(adb).
This module can find these runtimes and in which port they are listening.
Installation
From git
git clone https://github.com/mozilla/node-firefox-find-ports.git
cd node-firefox-find-ports
npm install
If you want to update later on:
cd node-firefox-find-ports
git pull origin master
npm install
npm
npm install node-firefox-find-ports
Usage
findPorts(options) // returns a Promise
where options is a plain Object with any of the following:
firefox: look for Firefox Desktop instances
firefoxOSSimulator: look for Firefox OS Simulators
firefoxOSDevice: look for local ports forwarded to connected devices
ignoreMultiplePortsPerDevice: if there are multiple local ports forwarded to the same remote debugging port on a device, report only the first that is found (default: true)
detailed: query each found runtime for more information, such as the version, build time, processor, etc. The additional data will be added to the entry under a new device field.
If no options are provided, or if options is an empty Object ({}), then findPorts will look for any runtimes, of any type.
Finding ports
var findPorts = require('node-firefox-find-ports');
// Return all listening runtimes
findPorts().then(function(results) {
console.log(results);
});
// Returns only Firefox OS simulators, this time with error handling
findPorts({ firefoxOSSimulator: true }).then(function(results) {
console.log(results);
}, function(err) {
console.log(err);
});
The output from the above code might look like the following:
After installing, you can simply run the following from the module folder:
npm test
To add a new unit test file, create a new file in the tests/unit folder. Any file that matches test.*.js will be run as a test by the appropriate test runner, based on the folder location.
We use gulp behind the scenes to run the test; if you don’t have it installed globally you can use npm gulp from inside the project’s root folder to run gulp.
Code quality and style
Because we have multiple contributors working on our projects, we value consistent code styles. It makes it easier to read code written by many people! :-)
Our tests include unit tests as well as code quality (“linting”) tests that make sure our test pass a style guide and JSHint. Instead of submitting code with the wrong indentation or a different style, run the tests and you will be told where your code quality/style differs from ours and instructions on how to fix it.
History
This is based on initial work on fx-ports by Nicola Greco.
The command line utility binary has been removed for this initial iteration, since pretty much all the existing applications using this module were just using the JS code directly, not the binary.
License
This program is free software; it is distributed under an
Apache License.
node-firefox-find-ports
This is part of the node-firefox project.
When runtimes have remote debugging enabled, they start a server that listens for incoming connections. Devices connected via USB can also have their remote debugging sockets forwarded to local TCP/IP ports by the Android Debug Bridge (adb).
This module can find these runtimes and in which port they are listening.
Installation
From git
If you want to update later on:
npm
Usage
where
optionsis a plain Object with any of the following:firefox: look for Firefox Desktop instancesfirefoxOSSimulator: look for Firefox OS SimulatorsfirefoxOSDevice: look for local ports forwarded to connected devicesignoreMultiplePortsPerDevice: if there are multiple local ports forwarded to the same remote debugging port on a device, report only the first that is found (default:true)detailed: query each found runtime for more information, such as the version, build time, processor, etc. The additional data will be added to the entry under a newdevicefield.If no
optionsare provided, or ifoptionsis an emptyObject({}), thenfindPortswill look for any runtimes, of any type.Finding ports
The output from the above code might look like the following:
Use the
detailedoption for additional information:Detailed output includes a lot more info:
Running the tests
After installing, you can simply run the following from the module folder:
To add a new unit test file, create a new file in the
tests/unitfolder. Any file that matchestest.*.jswill be run as a test by the appropriate test runner, based on the folder location.We use
gulpbehind the scenes to run the test; if you don’t have it installed globally you can usenpm gulpfrom inside the project’s root folder to rungulp.Code quality and style
Because we have multiple contributors working on our projects, we value consistent code styles. It makes it easier to read code written by many people! :-)
Our tests include unit tests as well as code quality (“linting”) tests that make sure our test pass a style guide and JSHint. Instead of submitting code with the wrong indentation or a different style, run the tests and you will be told where your code quality/style differs from ours and instructions on how to fix it.
History
This is based on initial work on fx-ports by Nicola Greco.
The command line utility binary has been removed for this initial iteration, since pretty much all the existing applications using this module were just using the JS code directly, not the binary.
License
This program is free software; it is distributed under an Apache License.
Copyright
Copyright (c) 2014 Mozilla (Contributors).