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-require-files

v0.0.2

Published

grunt plugin to generate AMD requires for listed files

Downloads

6

Readme

grunt-require-files

grunt plugin to generate AMD requires for listed files

I wrote this as a hack to generate a valid javascript source file declaring require() of file-globbed modules which I could load into a QUnit test runner that was being run via the grunt-qunit-istanbul plugin. The grunt-qunit-istanbul plugin only instruments (for coverage metrics) those source files which were loaded by the qunit test runner; therefore if your QUnit test modules did require all of your sources, you would be mislead into thinking you were covering more than you actually were.

Getting Started

This plugin requires Grunt.

If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

npm install grunt-require-files --save-dev

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

grunt.loadNpmTasks('grunt-require-files');

The "require_files" task

Overview

In your project's Gruntfile, add a section named require_files to the data object passed into grunt.initConfig().

grunt.initConfig({
  require_files: {
    options: {
      // Task-specific options go here.
    },
    your_target: {
      // Target-specific file lists and/or options go here.
    },
  },
})

Options

options.relativeTo

Type: String Default value: ./

A string value representing a path (to a directory or file), from which the required modules would be relative'ly loaded from.

options.callback

Type: String Default value: ''

A string value representing the callback function that would be invoked when the require()'d modules successfully load.

options.extraModules

Type: Array Default value: []

An array of module names to also load.

Usage Examples

Default Options

In this example, we have a test runner at test/js/tests.html, source modules in src/js, and test specs in test/js/specs that end in Spec.js. Additionally, we will require two extra modules: ModuleA and ModuleB.

grunt.initConfig({
  require_files: {
    options: {
      relativeTo: 'test/js/tests.html'
      callback: 'QUnit.start',
      extraModules: ['ModuleA', 'ModuleB']
    },
    files: {
      'build/test-requires.js': ['src/js/**/*.js', 'test/js/specs/**/*Spec.js'],
    },
  },
})

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.

Release History

  • 0.0.1 Initial release
  • 0.0.2 Add support for extra modules to require

License

Copyright (c) 2014 Kevin Mudrick. Licensed under the MIT license.