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

@wearethegarden/builder

v0.4.0

Published

A Gulp starting point for all projects.

Readme

builder

builder is the Gulp starting point for all projects. It provides all the relevant tasks, and is fully customisable.

Set up and installation

  1. Add builder to your project:
yarn install @wearethegarden/builder
  1. Create a config.json file within the tasks folder (in the root of your project) to define all the task-specific configuration.

Tasks and configuration

You can specify the source (src) and destination (dest—where applicable) of all tasks. You can also define the paths to watch when the watch task is running.

The following tasks and configuration are available via builder:

Clean

Intro

The clean task deletes a given folder (usually the source folder).

Config

  • src: The folder to be deleted.

Copy

Intro

The copy task will copy static assets to a given folder (usually the destination folder).

Config

  • src: The file(s)/folder(s) to copy—either a single file/folder, or an array of files/folders.
  • watch: The file(s)/folder(s) to watch.
  • dest: The destination folder to copy the static assets to.

Options

An array of options passed to gulp-changed.

CSS

Intro

The CSS task will take an SCSS file, run it through the PostCSS plugins (autoprefixer, cssnano, css-mqpacker), rename the file, generate sourcemaps, and output the file to the destination folder.

You can pass through either one SCSS file, or an array of files.

Config

  • src: The file(s) to compile.
  • watch: The file(s) to watch (Optional - If omitted, the src path will be used).
  • dest: The destination folder to write the CSS file to.

Options

An array of options to be passed to autoprefixer, mqpacker, gulp-rename, and gulp-sass.

Images

Intro

The images task will run the images through the relevant imagemin plugin (jpegtran, optipng, svgo), and output the files to the destination folder.

Config

  • src: The file(s) to compress.
  • watch: The file(s) to watch (Optional - If omitted, the src path will be used).
  • dest: The destination folder to write the compressed images to.

Options

An array of options to be passed to the imagemin plugins (jpegtran, optipng, svgo).

JS

Intro

The JS task will run the JS files through Webpack and output the file(s) to the destination folder. This task will search for a Webpack config (webpack.config.js) file in the root directory.

Config

  • src: The file(s) to run through Webpack.
  • watch: The file(s) to watch (Optional - If omitted, the src path will be used).
  • dest: The destination folder to write the JS file(s) to.

Lint

Intro

Linting tasks can be defined within the lint folder.

Config (foreach linting task)

  • src: The file(s) to lint.

Options

An array of options to be passed to the linter.

Serve

Intro

The serve task will start up Browsersync.

Options

An array of options to be passed to Browsersync.

Watch

Intro

The watch task will watch for any file changes and run the relevant task.

Each watch task will use the configured watch path for that task. If the watch path is the same as the src, then you don't need to define it as the src path will be used.