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

fixtures.js

v2.1.0

Published

Automatically find fixtures

Downloads

13

Readme

fixtures.js

Automatically load fixtures for tests from corresponding json files in the fixtures directory

Fixtures files

A fixtures file is a JSON file with the same name as your test file but a .json extension.

Examples:

Test file | Fixtures file ---------| ---------- feature1.js| feature1.json feature2.spec.js|feature2.spec.json

Location of fixtures file

Fixtures files can be placed in the following locations:

  1. Same directory as the test file
  2. in a fixtures folder under the test directory
  3. in a fixtures folder under any ancestor directory

For example, if the test file is at the following location:

/home/dude/projects/coolthing/specs/server/feature1/feature1.specs.js

The fixtures file may be located at the following locations (in priority order)

Priority | Fixtures file path ----------------|----------------- 1| /home/dude/projects/coolthing/specs/server/feature1/feature1.specs.json 2| /home/dude/projects/coolthing/specs/server/feature1/fixtures/feature1.specs.js 3|/home/dude/projects/coolthing/specs/server/fixtures/feature1.specs.js 4|/home/dude/projects/coolthing/specs/fixtures/feature1.specs.js 5| .. and so on all the way to the top until a fixtures dir is located

Usage

specs/features/fixtures/drwho.specs.json

{
	"name": "Dr. Who",
	"title": "Time Lord"
}

specs/features/drwho.specs.js

var expect   = require('expect.js')
var fixtures = require('fixtures.js')(__filename) // Automatically figure out filename and load

describe('Show attributes', function() {
  it('should get title', function() {
    var result = getTitle(fixtures.name)
    expect(result).to.equal(fixtures.title)
  }
}