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

gulp-yaml-update

v1.0.5

Published

A gulp plugin for updating fields in yaml documents.

Readme

gulp-yaml-update

CircleCI Coverage Status

A configurable gulp task to update fields in a yaml document.

Overview

Whenever I'm working on a swagger based API project I always run into a bit of difficulty in the build process when it comes to the way Swagger retrieves it's host from the swagger.yaml file. I thought it might be useful to have something that could easily swap out my host settings (at least) based on the environment I'm building for prior to the generation of the swagger.json file.

This custom gulp task is intended to address that situation. It is my hope that it will allow it's users to choose selected attributes to update at build time in order to make swapping from your localhost to other environments a bit easier.

Directives

The thought behind the array of directive objects is that I needed something that specified some sort of mapping between environment and property setting within the swagger definition.

Internally the plugin determines the current environment and selects which directives to apply based on that value. Those directives that exist in the array without an env property are simply always applied as is.

Another interesting twist is that this even allowed me to substitute values from the package.json into the modified swagger definition. This is useful for things like version or allowing you to control the title displayed in the swagger docs from a property in the package.json file.

Example Usage

const gulp = require('gulp');
const yamlUpdate = require('gulp-yaml-update');
const details = require('./package.json');
const runSequence = require('run-sequence');

const YAML_DIRECTIVES = [
    { path: 'version', value: details.version },
    { path: 'title', env: 'development', value: `${details.title} - Development` },
    { path: 'title', env: 'production', value: `${details.title} - Production` },
    { path: 'host', env: 'development', value: 'localhost:10010' },
    { path: 'host', env: 'production', value: 'some.production.host:81' }
];

gulp.task('yaml-update-dev', () => {
    return gulp.src([
        'api/swagger/swagger.yaml'
    ])
        .pipe(yamlUpdate({
            environment: 'development',
            directives: YAML_DIRECTIVES
        }));
});

gulp.task('yaml-update-prod', () => {
    return gulp.src([
        'api/swagger/swagger.yaml'
    ])
        .pipe(yamlUpdate({
            environment: 'production',
            directives: YAML_DIRECTIVES
        }));
});

gulp.task('default', (callback) => {
    runSequence('yaml-update-prod', callback);
});

References