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

v0.7.0

Published

Edit resources of EXE files.

Downloads

34

Readme

grunt-rcedit Version Build Status Build Status Dependency Status

Edit resources of EXE files.

Getting Started

This plugin requires Grunt ~0.4.0

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

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

grunt.loadNpmTasks('grunt-rcedit');

This plugin was designed to work with Grunt 0.4.x. If you're still using grunt v0.3.x it's strongly recommended that you upgrade, but in case you can't please use v0.3.2.

RcEdit task

Run this task with the grunt rcedit command.

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

Options

| Option | Type | Description | | ------------------| --------- | ----------- | | icon | String | Path to the application icon. | | file-version | String | Version number for the file. | | product-version | String | Version number for the product with which the file is distributed. | | version-string | Object | Key-value object containing the Version Information to replace in the .exe file. To get all the possible keys, you can check out the table below or open the .exe with a resource editor program like ResEdit. |

Usage

rcedit: {
  exes: {
    files: [{
      expand: true,
      cwd: 'dist/',
      src: ['**/*.exe']
    }],
    options: {
      'icon': 'res/icon.ico',
      'file-version': '0.0.1',
      'product-version': '0.0.2',
      'version-string': {
        'ProductName': 'Foobar',
        'FileDescription': 'Foobar',
        'CompanyName': 'Foobar Inc.',
        'LegalCopyright': 'Copyright 2015 Foobar Inc.'
      }
    }
  }
}

This task supports all the file mapping format Grunt supports. Please read Globbing patterns and Building the files object dynamically for additional details.

Version Information

The version-string supports the following properties (extracted from the MSDN):

| Property | Description | | --------------------- | ----------- | | Comments | Additional information that should be displayed for diagnostic purposes. | | CompanyName | Company that produced the file, for example "Microsoft Corporation" or "Standard Microsystems Corporation, Inc.". | | FileDescription | File description to be presented to users. This string may be displayed in a list box when the user is choosing files to install, for example, "Keyboard Driver for AT-Style Keyboards". | | FileVersion | Version number of the file, for example, "3.10" or "5.00.RC2". | | InternalName | Internal name of the file, if one exists, for example, a module name if the file is a dynamic-link library. If the file has no internal name, this string should be the original filename, without extension. | | LegalCopyright | Copyright notices that apply to the file. This should include the full text of all notices, legal symbols, copyright dates, and so on. | | LegalTrademarks | Trademarks and registered trademarks that apply to the file. This should include the full text of all notices, legal symbols, trademark numbers, and so on. | | OriginalFilename | Original name of the file, not including a path. This information enables an application to determine whether a file has been renamed by a user. The format of the name depends on the file system for which the file was created. | | ProductName | Name of the product with which the file is distributed. This string is required. | | ProductVersion | Version of the product with which the file is distributed, for example, "3.10" or "5.00.RC2". |

Meta

Contributors

License

Copyright (c) 2015 Daniel Perez Alvarez (unindented.org). This is free software, and may be redistributed under the terms specified in the LICENSE file.