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

jasmine-jsonpath

v0.1.0

Published

A plugin for jasmine to enable jsonpath(http://goessner.net/articles/JsonPath/)

Downloads

27

Readme

jasmine-jsonpath

A Plugin for Jasmine, to enable jsonpath(http://goessner.net/articles/JsonPath/) in matchers.

Installation

Download jasmine-jsonpath from here and put it in your jasmine test runner file( typically it's your SpecRunner.html). And you need jsonpath and json2 as well.

Methods

Let's say we have an object like this:

obj = {
    languages: [
        {
            type: "Dynamic",
            samples: ["Ruby", "Python"]
        },
        {
            type: "Static",
            samples: ["Java", "C"]
        },
        {
            type: "Dynamic",
            samples: ["JavaScript"]
        }
    ]
};

Then we want to get one special node by jsonpath:

it("should be able to get object by path", function() {
    var dynamic = jasmine.getNodeByPath(obj, '$.languages[?(@.type=="Dynamic")]');
    expect(dynamic[0].samples.length).toEqual(2);
    expect(dynamic[1].samples.length).toEqual(1);
});

check this out if you want to know all details about jsonpath

Matchers

Matcher toHasJsonPath can help you to verify whether an object has a given jsonpath or not:

it("should be able to deteming a path is existing", function() {
    expect(obj).toHasJsonPath('$.languages[0].type');
    expect(obj).toHasJsonPath('$.languages[?(@.type=="Static")]');
});

additionally, there is another more powerful(useful) matcher named toHasSchema, consider you have an object(request will be sent to server or response from server):

{
    languages: [
        {
            type: "Dynamic",
            samples: ["Ruby", "Python"]
        },
        {
            type: "Static",
            samples: ["Java", "C"]
        },
        {
            type: "Dynamic",
            samples: ["JavaScript"]
        }
    ],
    tools: {
        category: {
            name: "Common"
        }
    }
};

and to make sure none didn't break the schema and none will break it in the future, we need to write tests to ensure it:

it("should be able to tell an object has a special schema", function() {
    var schema = {
        languages: [
            {
                type: "Static",
                samples: []
            }
        ]
    };

    expect(obj).toHasSchema(schema);
});

Then, if someone accidently made a typo, say, languages to longuages, then the test will fail. You can make it more complex and more specified like:

it("should be able to tell an object has a special schema, more complex", function() {
    var schema = {
        languages: [],
        tools: {
            category: {
                name: "Common"
            }
        }
    };

    expect(obj).toHasSchema(schema);
});

And that's it.