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 🙏

© 2026 – Pkg Stats / Ryan Hefner

grunt-dependencies-injector

v0.1.0-beta.8

Published

A plugin that automate assets inclusion into html files

Readme

grunt-dependencies-injector

A plugin that automate assets inclusion into html files

Normally, this plugin is used with DocLine but you can use this plugin in any other project.

IMPORTANT The develpment of this plugin was started inside DocLine but it was refactored
to be standalone from DocLine. Until the end of the DocLine's development
this plugin will be updated to work with DocLine. After the end of the development,
we will work more on this

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-dependencies-injector --save-dev

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

grunt.loadNpmTasks('grunt-dependencies-injector');

The "dependencies_injector" task

Overview

In your project's Gruntfile, add a section named dependencies_injector to the data object passed into grunt.initConfig().
Look the configuration is for the index_compiler task that is one of the task run by dependencies_injector

grunt.initConfig({
    index_compiler: {
        build: {
            dir: '',
            pkg_version: '',
            src: [
            ]
        },
        compile: {
            dir: '',
            pkg_version: '',
            src: [
            ]
        }
    },
    dependencies_injector: {
        build: {},
        compile: {}
    }
})

Options

You can customize the settings for the selected target 'build' or 'compile'

build.dir

Type: String Where locate the processed index.html

build.pkg_version

Type: String The version to use for building files

build.src

Type Array A list of paths where find the assets to include in the processed index.html file

compile.dir

Type: String Where locate the processed index.html

compile.pkg_version

Type: String The version to use for building files

compile.src

Type Array A list of paths where find the assets to include in the processed index.html file

Usage Examples

Default Options

These are the plugin's main configurations but there are many others sub-configurations for
the 'clean', 'copy', 'concat', 'ngAnnotate', 'uglify' tasks. These tasks use some configurations to find the
resources. Please check the Wiki of this repository.

grunt.initConfig({
    index_compiler: {
        /**
         * During development, we don't want to have wait for compilation,
         * concatenation, minification, etc. So to avoid these steps, we simply
         * add all script files directly to the '<head>' of 'index.html'. The
         * 'src' property contains the list of included files.
         */
        build: {
            dir: '.',
            pkg_version: '<%= pkg.version %>',
            src: [
                '<%= build_dir %>/**/*.css',
                '<%= build_dir %>/**/*.js'
            ]
        },
        /**
         * When it is time to have a completely compiled application, we can
         * alter the above to include only a single JavaScript and a single CSS
         * file. Now we're back!
         */
        compile: {
            dir: '.',
            pkg_version: '<%= pkg.version %>',
            src: [
                '<%= vendor_files.css %>',
                '<%= concat.compile_js.dest %>'
            ]
        }
    },
    dependencies_injector: {
        build: {},
        compile: {}
    }
})

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.

License

Copyright (c) 2015 Lorenzo Savini. Licensed under the Apache-2.0 license.