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 🙏

© 2025 – Pkg Stats / Ryan Hefner

banger

v0.0.15

Published

Gulp-based build system, inject tasks into lifecyce, so it can be extended by user tasks.

Downloads

22

Readme

Gulp-Based Build System

js-standard-style GitHub issues GitHub license

This project uses Gulp to build NodeJS based apps.

Purpose

The basic tenet of this project is to provide a life-cycle base build system to automate NodeJS application(s). The life-cycle provide points we can attach tasks to. This provides the ability to provide an extensible base of tasks to build any application.

Life-cycle

Each life-cycle is made up of phases, each depending on the previous in the chain to have executed. You attach tasks to a phase for it to be run. Each task associated with a phase is run in parallel.

IMPORTANT: A task must have no dependency other than the phase.

There are in fact multiple life-cycles, Clean and Default.

| Name | Description | | ---------- |:------------------------------------------------------------- | | pre-clean | execute processes needed prior to the actual project cleaning | | clean | remove all files generated by the previous build | | post-clean | execute processes needed to finalize the project cleaning |

Default Lifecycle

| Name | Description | | ----------------------- |:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | validate | validate the project is correct and all necessary information is available. | | initialize | initialize build state, e.g. set properties or create directories. | | resources | generate resources for inclusion in the package. | | compile | compile the source code of the project. | | test-compile | compile the test source code into the test destination directory | | test | run tests using a suitable unit testing framework. These tests should not require the code be packaged or deployed. | | dist | take the compiled code and package it in its distributable format, such as a JAR. |

Validate

The validate phase is where we check files:

  • well-formed package.json
  • lint code (JavaScript,TypeScript,SASS)

Initialize

Create directories and any other necessary project structure before project can be built.

Resources

Generate resources used by the project:

  • image sprites
  • source-maps

Compile

Compile the code (if necessary), for instance, if you are using TypeScript.

Compile Tests

Compile the code (if necessary), for instance, if you are using TypeScript.

Test

Run Unit Tests

Create Distribution

Generate the distribution.

Old Task Order

default: validate-package-json parallel: clean ts-lint check-js-style check-js-quality parallel: scripts-TypeScript scripts-JavaScript copy: parallel: styles-vendor-dist styles-dist scripts-JavaScript-dist html images

New task Order

clean

default: validate: package-json ts-lint js-lint sass-lint initialize: log resources: html images compile: ts-compile js-compile test: unit-test dist: styles-vendor styles-app js

Release Process

  • commit all changes to include in the release
  • edit the version in package.json (respect semver)
  • update CHANGELOG.MD
  • commit
  • git tag <version>
  • git push --tags
  • draft the release on GitHub (add description, etc)
  • npm publish

Authors

Mark Small

License

This project and all associated source code is licensed under the terms of the MIT License.