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

@middlebury/gulp-config

v2.0.4

Published

Middlebury shared gulp configuration with optional config for jekyll usage

Downloads

73

Readme

Middlebury Gulp Config

Create gulp configs for static sites (jekyll) or other frontend systems

Requirements

  • Node.js ^18.16.0

Getting started

1. Install packages

# main gulp package is also required as a peer dependency
npm install --save-dev gulp @middlebury/gulp-config

2. Add gulp config file to root of your project.

// gulpfile.js

import { createConfig } from '@middlebury/gulp-config';

export const { dev, build } = createConfig();

Gulp tasks made available by createConfig():

dev, build, clean, scripts, styles, watch, serve

3. Add scripts

Add the dev and build tasks to your package.json.

{
  "scripts": {
    "start": "gulp dev",
    "build": "gulp build"
  }
}

gulp build automatically sets NODE_ENV=production

Configuration

The gulp config comes with some standard assets paths by default.

const defaultOptions = {
  clean: './dist',
  // Set up for Sass by default
  styles: {
    src: './src/scss/*.scss',
    watch: './src/scss/**/*.scss',
    dest: './dist/css'
  },
  // Scripts use rollup to bundle into a single file
  // so the destination is a file name, not a folder.
  scripts: {
    src: './src/js/index.js',
    watch: './src/js/**/*.js',
    dest: './dist/js/bundle.js'
  },
  images: {
    src: './src/img/*.{jpg,png,svg}',
    watch: './src/img/*.{jpg,png,svg}',
    dest: './dist/img'
  },
  browserSyncOptions: {
    open: false,
    notify: false,
    server: {
      baseDir: dist()
    },
    ghostMode: false
  },
  afterBuild: [],
  beforeBuild: [],
  typescriptBuild: false
};

Pass your own config to createConfig(myOptions) and they will be merged with the defaults.

Jekyll configuration

If you have a jekyll website, you can use a preset gulp config that will run jekyll via command line.

import { createJekyllConfig } from '@middlebury/gulp-config';

export const { dev, build } = createJekyllConfig();

The Jekyll config differs slightly like using _site as dist. See examples directoy how to set up your files.

Releasing

You'll need to be part of the @middlebury npm org to publish.

npm version <patch|minor|major>
git push --tags
git push
npm publish