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

grunt-weinre

v0.0.3

Published

Grunt task to run a weinre server to debug your mobile web site/app.

Readme

grunt-weinre

Run weinre as a grunt task for easy configuration and integration with the rest of your workflow

NPM version Dependency Status

Getting Started

If you haven't used grunt before, be sure to check out the Getting Started guide, as it explains how to create a gruntfile as well as install and use grunt plugins. Once you're familiar with that process, install this plugin with this command:

npm install grunt-weinre --save-dev

Then add this line to your project's Gruntfile.js gruntfile:

grunt.loadNpmTasks('grunt-weinre');

Documentation

Usage

The minimal usage of weinre runs with no options:

weinre: {
  dev: {}
}

Recommended Usage

The default HTTP port of 8080 is pretty popular, so offsetting it by 2 may help you dodge a collision. Also setting the boundHost to -all- will let your mobile devices connect via your local ip address, since the default localhost won't work for them.

weinre: {
  dev: {
    options: {
      httpPort: 8082,
      boundHost: '-all-'
    }
  }
}

Usage with all available options(with their default values):

weinre: {
  dev: {
    options: {
      httpPort: 8080,
      boundHost: 'localhost',
      verbose: false,
      debug: false,
      readTimeout: 5,
      deathTimeout: 15
    }
  }
}

Running weinre concurrently

A common use case is to run weinre with other tasks concurrently. This can be achieved with the following config for the grunt-concurrent plugin which runs weinre, nodemon, node-inspector, and watch in a single terminal tab:

concurrent: {
  dev: {
    tasks: ['weinre', 'nodemon', 'node-inspector', 'watch'],
    options: {
      logConcurrentOutput: true
    }
  }
}

Options

httpPort

Type: Number Default: 8080

Port to run the http server on.

boundHost

Type: String Default: 'localhost'

IP address to bind the server to.

verbose

Type: Boolean Default: false

Print more diagnostics.

debug

Type: Boolean Default: false

Print even more diagnostics.

readTimeout

Type: Number Default: 5

Seconds to wait for a client message.

deathTimeout

Type: Number Default: 3 * readTimeout

Seconds to wait to kill client.

Changelog

0.0.2 - Fixed error logging, allowed weinre to be listed as an app dependency.

0.0.1 - Initial release.