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-build-info-angular-injector

v1.0.6

Published

Allows you to pass compile time variables to grunt which will then get injected into angular for usage at runtime.

Downloads

1

Readme

grunt-build-info-angular-injector

Allows you to inject information about the build into angular. Such as the branch the build came from, the version and the build number.

Install

$ npm install grunt-build-info-angular-injector --save

Usage

grunt.loadNpmTasks('grunt-build-info-angular-injector');

grunt.initConfig({
  injectBuildInfo: {
    module: 'my.angular.module',
    providerName: 'myBuildInfoProvider',
    target: 'src/buildInfoService.js'
  }
});

grunt.registerTask('default', ['injectBuildInfo']);

grunt default --buildNumber=${env:BUILD_NUMBER} --branch=${env:GIT_BRANCH} --buildName=${env:JOB_NAME}

Options

These are the configuration options you can pass to grunt.

module

Type: string Default: buildInfo

The name of the already existing angular module to attach this provider to.

providerName

Type: string Default: buildInfo

The name the provider will have within your application, ie. the name of the injectable.

target

Type: string Default: src/buildInfoService.js

The target file for the provider. This will be created, you will still have to include it in your template.

Parameters

These are the command line parameters which you can call grunt with to be injected into the provider.

  • buildNumber e.g. --buildNumber=21
  • buildName e.g. --buildName=dev
  • branch e.g. --branch=master