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

grunt-jasmine-chromeapp

v1.10.0

Published

Grunt task to run jasmine tests in a chrome packaged app

Downloads

20

Readme

grunt-jasmine-chromeapp

Run jasmine specs in a Chrome Packaged App

Build Status

Getting Started

This plugin requires Grunt ~0.4.0

If you haven't used Grunt before, be sure to check out the Getting Started guide, which explains how to create your grunt file. Once you're familiar with the process, this plugin can be installed as:

npm install grunt-jasmine-chromeapp --save-dev

Once the plugin has been installed, it may be enabled with this line of JavaScript:

grunt.loadNpmTasks('grunt-jasmine-chromeapp');

Jasmine Task

Run this task with the grunt jasmine_chromeapp command.

Automatically builds and maintains the spec runner and reports results back to the grunt console. Starts chrome with a dynamically created packaged application which runs jasmine specs. The package reports results back to a web server run by the plugin, which then reports back to the console. This structure is chosen becasue selenium is unable to debug or instrument packaged applications directly.

Customize your SpecRunner

Use your own files in the app to customize your tests.

Options

src

Type: String|Array

Your source files and specs. These are the files you are testing.

options.paths

Type: String|Array

Listing of which files should be included as script tags in the test runner. If not set, defaults to all files listed as source files, but can define a subset of those files to support copying non-js files, or other support files which should not be directly included.

options.keepRunner

Type: Boolean Default: false

Prevents the auto-generated app from being automatically deleted, and leave the browser open.

options.binary

Type: String Default: undefined

Specify the locations of google-chrome to run for testing. Defaults to the per-platform default locations specified by chromedriver if not specified.

options.flags

Type: Array Default: []

Additional command-line flags to pass to chrome. These are appended to the default flags used for instantiation: --no-first-run, --force-app-mode, --apps-keep-chrome-alive-in-tests, --load-and-launch-app, and --user-data-dir. --no-startup-window is also used for the Mac platform.

options.timeout

Type: Number Default: 30000

How many milliseconds to wait for the browser to start up before failing.

options.outfile

Type: String Default: .build

The directory to stage the chrome app into.