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 🙏

© 2026 – Pkg Stats / Ryan Hefner

android-api

v0.0.1

Published

A Node interface for some Android and ADB commands

Readme

Android API

##Overview

Android API is a Node package that lets you connect to the adb and android command lines with a simple interface.

It is meant to be promise based, and let you do common tasks available to the Android command lines, such as:

  • Create a project, either Gradle or Ant compliant.
  • Compile it as a debuggable or releasable apk.
  • Connect to one, or many, devices or emulators.
  • Install an apk or push any file to any of your devices.

##Promise based - almost

The library uses promises to make almost every calls.

There is one single exception. Since promises are meant to be started and ended relatively fast, logcat (a long running process) gets new logs from your applications through a callback. You can see more on the examples.js file.

##Examples

There's a file which contains a lot of chained examples of app usage. It's also a quick example on how to chain calls to get the best results.

##Procedure to follow

Note: Make sure you have adb and android commands accessible from your command line.

  1. Always start calling android_api.init(). With this call, you ensure the adb command is accessible and the server is started.
  2. create a then response to this, and call inside the next process, for instance, android.logcat. Don't forget to return the promise to the calling function.
  3. Give it "1", an object { output : 'json' } and a callback, which returns the logcat new logs. "1" notes you want the first device, but it could be a device id in the form of an array: [device_id]. The output marked in json returns each logcat entry as a json entry, instead of plain text.
  4. Put a catch method afterwards, so it gets any previous error.
  5. Finally, mark the end of this procedure with done.

Here it is, also available in the examples.js file.

   android.init()
    .then(function() {
      return android.logcat(
        "1",
        { output : 'json' },
        function(logcat_data) {
          console.log(logcat_data);
        });
      }
    )
    .catch(function(err) {
      console.error(err);
    })
    .done();

##What's working, already?

The library currently lets you:

  • Init adb server.
  • Get the connected devices to the computer.
  • Compile an ant based project.
  • Start listening to logcats.

##Documentation

The whole library is JSdoc compliant. If you clone the package, you can run:

npm run-script docs

Inside the package folder, and it will create all the documentation structure into ./docs/. You can change the path to where it is stored by modifying the package.json file.

##Collaboration

The library is still in alpha, and multiple methods are defined but empty. If you wish to collaborate and make them, don't hesitate to make a pull request!

##Testing

Awwwww! I started coding blindlessly. I've been testing with my devices but I have not deeply tested it, unfortunately. If you wish to start testing it, I'm actually free to suggestions in terms of libraries and procedures.

##License

Copyright (c) 2014, Sergi Juanola [email protected]

Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.