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-combine-js

v0.1.14

Published

combine js modules into one file

Downloads

12

Readme

grunt-combine-js

combine js modules into one file

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-combine-js --save-dev

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

grunt.loadNpmTasks('grunt-combine-js');

The "combine_js" task

Overview

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

The idea behind this plugin is that you can pick and choose from your javascript modules to combine them into one file with the name and destination of your choosing.

In the grunt file you will have 4 options:

  1. "src" - this is the path to the json build file which will contain the JS module paths and the destination name and destination folder.
  2. "combine_folder" - you may have a folder that contains scripts you also want to include in your final js file, for plugins perhaps.
  3. "additional_files" - literally just extra scripts you would like included, so this could be scripts that are to be included in every js file build, e.g. a pub/sub script.
  4. "base_files" - this will allow you to set some predefined files to include in every build, these will be inserted before the 'src' files.

In the JSON file you use for "src" there are the following options:

  1. "modules" - an array of file paths to the files you want to combine *REQUIRED
  2. "dest_name" - what the file will be called when built *REQUIRED
  3. "dest_path" - where the built file should go *REQUIRED
  4. "useBase" - by default this is true, if you don't want to use a set of base files then set to false

The order these scripts will be combined in the final file is:

  1. additional_files
  2. combine_folder
  3. base_files
  4. src

Usage Examples

grunt.initConfig({
  combine_js: {
    files: [{
      src: '/path/to/json/file/build.json',
      combine_folder: '/path/to/directory/where/all/files/will/be/combined/',
      additional_files: [
        '/path/to/extra/scripts/file-a.js',
        '/another/path/to/extra/scripts/file-b.js'
      ],
      base_files: [
        'path/to/file.js',
        'path/to/another/file.js'
      ]
    }]
  },
});

Example JSON build file

[
    {
        "modules": [
            "src/assets/scripts/modules/file-a.js",
            "src/assets/scripts/modules/file-b.js"
        ],
        "dest_name": "test_a.js",
        "dest_path": "dist/_scripts/",
        "useBase": false
    },
    {
        "modules": [
            "src/assets/scripts/modules/file-c.js",
            "src/assets/scripts/modules/file-d.js"
        ],
        "dest_name": "test_b.js",
        "dest_path": "dist/_scripts/"
    }
]

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)