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

ca-buildmodule

v1.2.5-0

Published

One module to build them all. This contains the webpack gulp tasks that should be used universally within frontend repos.

Downloads

2

Readme

ConsumerAffairs Universal Build module

Of supreme buildocity

This module is to be installed atop any of our frontend modules that we want to automatically have our webpack/karma tasks available.

Default tasks and aliases are located inside of the tasks folder.

Usage

  • In the module you'd like to extend with this ensure you have gulp.
    • npm install --save-dev gulp
  • Install this module: npm install --save-dev ca-buildmodule
  • Create/modify your gulpfile.js to include default tasks, as shown below:
(function() {
    'use strict';

    var CABuild, gulp;
    gulp = require('gulp');
    // We need to instansiate the build module, and then hand it our current modules gulp binary
    // and any config we want to pass to customize this build
    CABuild = new (require('ca-buildmodule'))(gulp, { ... config ... });

    // You'll now have all of the default task
    // But dont let that stop you from creating some project-specify tasks as well
    gulp.task('do-other-stuff', function(){ ... });

}());
  • You can confirm that you have default tasks by running gulp --tasks. You should see quite the list.
  • Config items overwrite the defaults variable in this modules config file.
Update Notice

The main reason why this module was created was because the build tasks located within were getting manually cloned across projects, and maintaining fixes/improvements became nearly impossible.

This is written in a way to be both generic and customizable, but updates are likely to happen as technology changes and improvements are discovered. If you have a need for feature support please talk to your Team Lead and hopefully it can get worked in, and even more hopefully ... you'll be willing to contribute!

good day

Stylelint Notice

In order to run clear linting without packing use "gulp l" or "gulp lint"