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

v0.1.2

Published

Perforce commands for Grunt

Downloads

34

Readme

grunt-p4

Execute common p4 commands from your Grunt build.

Note that for these commands, file paths must be specified in the task options, not the task's list of files. Grunt strips the task file list of non-existent files, and often (especially in the case of p4 sync) the files you intend to sync may not yet exist.

All commands are multi-tasks and can be configured as such.

Installing

Install at the project level, usually to your dev-dependencies:

npm install grunt-p4 --save-dev

Supported Commands

revert

Revert a list of files. (See p4 revert)

Options

  • paths - Array; a list of file paths

Example


grunt.initConfig({
  p4revert: {
    options: {
      paths: [
        './src/version.js',
        './docs/version.md'
      ]
    }
  }
);

sync

Synchronize local files with a remote repository. (See p4 sync)

Options

  • paths - Array; a list of file paths
  • force - Boolean; when true, force the sync, even if the local workspace already has the file.
  • preview - Boolean; when true, displays the results of the sync without actually performing the sync.

Example


grunt.initConfig({
  p4sync: {
    options: {
      force: true,
      preview: false,
      paths: [
        './src/version.js',
        './docs/version.md'
      ]
    }
  }
);

edit

Check out a file for modification in the local workspace. (See p4 edit)

Options

  • paths - Array; a list of file paths
  • preview - Boolean; when true, displays the results of the sync without actually performing the sync.

Example


grunt.initConfig({
  p4edit: {
    options: {
      preview: false,
      paths: [
        './src/version.js',
        './docs/version.md'
      ]
    }
  },
});

submit

Submit a changelist to the repository. (See p4 submit)

Options

  • description - String; the commit message. If omitted, defaults to 'Automated submit via Grunt'
  • changelist - Number; the changelist number. If omitted, the operation is not performed.

Example


grunt.initConfig({
  p4submit: {
    options: {
      description: 'A commit message',
      changelist: 12345
    }
  },
});

Contributing

Fork this library and run npm install. This library is built using Grunt, which must be installed globally (npm install -g grunt).

Once installed, run grunt to enter watch mode, which will run unit tests with each change. (Run grunt test for a single test run.)

All new code must have associated unit test coverage prior to pull request acceptance.