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-humans-txt

v0.2.1

Published

Grunt task to build a humans.txt file using data from any JSON file, i.e package.json file or directly from your Gruntfile. A humans.txt is a TXT file that contains information about the different people who have contributed to building the website.

Downloads

3

Readme

grunt-humans-txt

Generate a humans.txt file for the website.

Build Status

Getting Started

This plugin requires Grunt ~0.4.1

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-humans-txt --save-dev

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

grunt.loadNpmTasks('grunt-humans-txt');

The "humans_txt" task

Overview

Run this task with the grunt humans_txt command.

The task creates a humans.txt file using data from any JSON file, i.e package.json file or directly from your Gruntfile. A humans.txt is a TXT file that contains information about the different people who have contributed to building the website.

Task targets, files and options may be specified according to the grunt Configuring tasks guide.

Options

intro

Type: String Default value: 'The humans responsible & colophon'

A string value that is used in the head of the file.

commentStyle

Choices: 'c', 'u', 'p' Default value: 'c'

Style of comments with section titles. Use 'c' for C style, 'u' for unix style, and 'p' for PHP style.

/* C STYLE COMMENT */

# UNIX STYLE COMMENT

// PHP STYLE COMMENT

tab

Type: String Default value: '\t'

A string value that is used to advance nested values.

includeUpdateIn

Type: String or false Default value: 'site'

Include current date as Last update in section with specified name. Set to false to disable.

Usage Examples

Local Content

In this example, the content options includes the data to be used. Each root item is a section.

grunt.initConfig({
  pkg: grunt.file.readJSON('package.json'),
  humans_txt: {
    options: {
      commentStyle: 'u',
      content: {
        'team': [ {
          'Web developer': 'Neil Barton',
          'Site': 'http://www.roughcoder.com',
          'Twitter': '@roughcoder',
          'Location': 'London, UK'

          },
          {
            'Ruby guy': 'Sam Jones',
            'Site': 'http://www.samjones.com',
            'Twitter': '@samjones'
          }
        ],
        'thanks': [
          {
            'Name': 'David Jones',
            'Website': 'www.google.com'
          }
        ],
        'site': [ {
            'Version': '<%= pkg.version %>',
            'Site Url': '<%= pkg.homepage %>',
            'Keywords': '<%= pkg.keywords %>',
            'Language': 'English',
            'Technology': 'node.js, apache'
          }
        ]
      },
    },
    dest: 'humans.txt', 
  },
})

External Content

In this example, the content is read from external file.

grunt.initConfig({
  humans_txt: {
    options: {
      content: grunt.file.readJSON('humans.json')
    },
    dest: 'humans.txt', 
  },
})

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

  • 2013-09-09 v0.2.1 Test tweak to allow Travis
  • 2013-08-20 v0.2.0 Extended variability, tests
  • 2013-06-11 v0.1.0 Initial task.