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

v0.0.3

Published

no, require all!

Downloads

2

Readme

grunt-requireall

no, require all!

Getting Started

This plugin requires Grunt ~0.4.5

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-requireall --save-dev

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

grunt.loadNpmTasks('grunt-requireall');

The "requireall" task

Overview

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

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

Options

options.assetRootPath

Type: String Default value: './assets/'

资源根目录,要require的资源文件都在该资源目录中查找

options.ext

Type: String Default value: '.required.js'

处理后的文件的后缀,比如list.js -> list.required.js , list.debug.js -> list.debug.required.js

options.htmlDir

Type: String Default value: 'html'

require的html文件的目录名,该目录名会位于opitons.assetRootPath指定的资源根目录下

options.jsDir

Type: String Default value: 'js'

require的js文件的目录名,该目录名会位于opitons.assetRootPath指定的资源根目录下

options.cssDir

Type: String Default value: 'css'

require的css文件的目录名,该目录名会位于opitons.assetRootPath指定的资源根目录下

options.lessDir

Type: String Default value: 'less'

require的less文件的目录名,该目录名会位于opitons.assetRootPath指定的资源根目录下

options.tmplDir

Type: String Default value: 'tmpl'

require的tmpl文件的目录名,该目录名会位于opitons.assetRootPath指定的资源根目录下

options.tmplEngine

Type: String Default value: 'dot'

require的tmpl后缀的文件内容,将会作为模板,使用模板引擎编译为function,tmplEngine则是模板引擎的包名,默认使用dot

options.tmplEngineCompileMethod

Type: String Default value: 'template'

模板引擎编译模板的方法名称,默认为template,代码示例:require(options.tmplEngine)[options.tmplEngineCompileMethod]

options.tmplRequireAfter

Type: Functiton Default value: Function

模板引擎编译后的function代码,需要经过该function的处理

Usage Examples

Default Target

grunt.initConfig({
  requireall: {
    options: {},
    files: {
      'build/': ['src/*.debug.js'],
    },
  },
});

Test Target

grunt.initConfig({
  requireall: {
    test_target: {
      options: {
        assetRootPath: './test/fixtures/assets',
      },
      src: './test/fixtures/src/*.js',
      dest: './test/fixtures/build/',
    }
  }
});

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

(Nothing yet)