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

@netzstrategen/gulp-task-collection

v4.1.4

Published

A collection of gulp tasks.

Downloads

36

Readme

netzstrategen Gulp tasks collection

Commonly used Gulp tasks shared across projects.

Supported tasks

  • Clean /dist folder
  • Sass compilation
  • JS compilation
  • Image compression
  • SVG icon sprite generation
  • Inline SVG files

Installation

  1. npm i @netzstrategen/gulp-task-collection
  2. require in project Gulpfile (see sample.gulpfile.js)
  3. Customise asset paths in project package.json (see package.json)

Available commands

  • gulp: Default task runs (in order) fonts, icons, images, styles, scripts and then watches for changes

  • gulp build: Build assets (fonts, icons, images, styles, scripts)

  • gulp build:production: Build production-ready assets

  • gulp clean: Clean /dist folder

  • gulp styles and gulp styles:production: Sass compilation

  • gulp scripts and gulp scripts:production: JS compilation

  • gulp fonts: Copy fonts to /dist folder

  • gulp icons: Generate SVG icon sprite from folder of individual SVG icons

  • gulp images: Image compression and inline SVG

styles / scripts task options

Option | Effect :--- | :--- --minify | Additionally generate minified files, suffixed with .min. Defaults to true in production builds. --sourcemaps | Add source mappings to compiled files. Defaults to true in non-production builds. --fail-after-error | See section Continuous Integration below for details. --concat | Concatenate CSS/JS asset files into a single aggregate file.

You can pass an options object inside gulpPaths.scripts/gulpPaths.styles in your package.json to set options for each respective task.

Continuous Integration

To not break the watch process, all tasks are continued by default, even if one of the tasks produces an error, so gulp will always exit with code 0.

Continuous Integrations and build scripts can use the flag --fail-after-error to make gulp exit after an error with an exit code > 0. By default, --fail-after-error is false for both dev and production builds.

Upgrading to v3

Version 3.0 introduces some changes to the behavior in v2:

  • concat is now false by default for css and js. v2 was concatenating js, but not css. To keep this behavior, set gulpPaths.scripts.options.concat: true inside your project's package.json.
  • the --production flag is gone. To run a build for production environments, please use the corresponding styles:production and scripts:production tasks.
  • the --outputStyle flag is gone. It has been replaced by --minify.
  • the option --sourcemaps is enabled by default for development / non-production builds.

Authors