npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

node-firefox-find-app

v1.1.0

Published

Find an installed app on a runtime

Downloads

36

Readme

node-firefox-find-app Build Status

Find if an app is installed on a runtime.

This is part of the node-firefox project.

Current limitations

We do not support Windows yet. But there are placeholders in the code marked with TODO: Windows that indicate where the Windows code would need to be added. If you want to contribute, those are the gaps that need to be filled in order for this to work on Windows.

NOTE

This is a work in progress. Things will probably be missing and broken while we move from fxos-findapp to node-firefox-find-app. Please have a look at the existing issues, and/or file more if you find any! :-)

Installation

From git

git clone https://github.com/mozilla/node-firefox-find-app.git
cd node-firefox-find-app
npm install

If you want to update later on:

cd node-firefox-find-app
git pull origin master
npm install

npm

This module is not on npm yet.

Usage

findApp(options) // returns a Promise

where options is a plain Object which must contain the following:

  • manifest: the manifest contents, in JSON format
  • client: the remote client where we want to find if this app is installed

If no options are provided, or if options is an empty Object ({}), then findApp will fail (how can you find you don't know what app exactly in you don't know where?)

Finding apps in simulators, using the manifest JSON contents

var findApp = require('node-firefox-find-app');
var startSimulator = require('node-firefox-start-simulator');
var connect = require('node-firefox-connect');
var manifest = loadJSON('/path/to/manifest.webapp'));

startSimulator().then(function(simulator) {

  connect(simulator.port).then(function(client) {

    findApp({
      manifest: manifest,
      client: client
    }).then(function(result) {

      if (result.length === 0) {
        console.log('App is not installed');
      } else {
        console.log('Found app!', result);
      }

      client.disconnect();
      stopSimulator(simulator);

    });

  });

});

You can have a look at the examples folder for a complete example.

Running the tests

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 fxos-findapp by Nicola Greco.

License

This program is free software; it is distributed under an Apache License.

Copyright

Copyright (c) 2015 Mozilla (Contributors).