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

aladdin

v0.3.3

Published

Phantom test runner for Jasmine

Downloads

17

Readme

Aladdin

A whole new world of javascript testing.

Installation

brew install phantomjs
sudo npm install aladdin -g

Loading source files

By default phantom-jasmine will look for a json file in spec/config.json. Use this to list all the scripts you want to load before your specs. e.g.

[ 
  'lib/jquery.js',
  'app/**/*.js'
]

If you want to put this file elsewhere use the --config flag, e.g.

aladdin --config tests/config.json

Running Tests

aladdin

Or run specific specs

aladdin spec/path/my_spec.js
aladdin spec/path/

If everything works you should see output like this in your terminal:

Starting...

Failures:

  1) failure should fail for the example.
     Expected false to be truthy.

Finished in 0.009 seconds
21 specs, 1 failures

Options

--format, -f [type]   Specify a format type for the spec output. Options "doc"
--config, -c [file]   Path to config file
--trace, -t           Show full stack traces