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-files-check-oldschool

v900.1.4

Published

Grunt plugin to apply regular expressions on files and check their validity.

Downloads

7

Readme

grunt-files-check

Grunt plugin to apply regular expressions on files and check their validity.

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-files-check-oldschool --save-dev

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

grunt.loadNpmTasks('grunt-files-check-oldschool');

The "files_check" task

Overview

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

grunt.initConfig({
  files_check: {
    your_target: {
      options: {
        pattern: /* your regex */
      },
      src: /* the files that will be checked */
    },
  },
})

Options

options.pattern

Type: String Default value: /^$/

The regex that will by applied on every file.

options.excluded

Type: Array Default value: []

An array which contains the files that will not be checked

options.verbose

Type: Array Default value: false

When set to true the task will display the files that have been checked.

options.maxFileNameWidth

Type: Integer Default value: 40

Define the max width used to display a file name in the output. When the file is too long, ellipsis -> '...' are written.

options.output

Type: String Default value: null

Define file name where log content will be saved.

Usage Examples

Check for console.log

In this example, we check every js files in the app/scripts folder to ensure that there no console.log anymore. We exclude the app/scripts/debug which contains files we do not want to check.

grunt.initConfig({
  console_log: {
    your_target: {
      options: {
        excluded: ['app/scripts/debug/**/*.js'],
        pattern: /console\.log/
      },
      src: ['app/scripts/**/*.js']
    },
  },
})

Check for console.log with output formatting

Same example as the previous one, except that we are going to format the output. We display the files that have been checked with the option verbose: true and we fix the max width used to display files name to 100 characters (large console) with the option maxFileNameWidth: 100.

grunt.initConfig({
  console_log: {
    your_target: {
      options: {
        excluded: ['app/scripts/debug/**/*.js'],
        pattern: /console\.log/,
        verbose: true,
        maxFileNameWidth: 100
      },
      src: ['app/scripts/**/*.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.