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-fixtures2js

v0.1.3

Published

Convert your fixtures into a JS object for use in tests.

Downloads

14

Readme

grunt-fixtures2js

Build Status

Ever wondered how to access static text-based files (e.g. JSON, HTML) from your tests? grunt-fixtures2js makes things easier for you by creating a JS file out of your fixtures, containing an object where file contents mapped to their filenames. You can then just include that file in your tests and voilá!

Installation

You can install grunt-fixtures2js via npm:

$ npm install --save-dev grunt-fixtures2js

Usage

You can configure your fixtures2js tasks as follows:

fixtures2js: {
    default: {
        files: {
            "my-fixture-file.js": "fixtures/*"
        }
    }
}

Options

  • head (defaults to window.FIXTURES = ) a string to insert before the generated JSON.
  • tail (defaults to ;) a string to insert after the generated JSON.
  • postProcessors (defaults to {}) a string to string object where keys are minimatch patterns and values are one of default, json, base64 or bytearray. If a file is not matched by any pattern, default is used.

Examples

If you have a configuration like this:

fixtures2js: {
    default: {
        options: {
            head: "processFixtures(",
            tail: ");",
            postProcessors: {
                "**/*.json": "json"
            }
        },
        files: {
            "my-fixture-file.js": "fixtures/*"
        }
    }
}

Running grunt fixtures2js:default will read the contents of the files in the fixtures/ folder, and generate a my-fixture-file.js like this:

processFixtures({
    "fixtures/one-fixture-file.txt": "The contents of the fixture file here",
    "fixtures/other-fixture-file.txt": "The contents of another fixture file here",
    "fixtures/stuff.json": {
        "foo": "bar"
    }
});