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

one-gulp

v0.3.3

Published

a ready to use set of gulp tasks

Downloads

6

Readme

one-gulp

[WIP] a ready to use set of gulp tasks

install

If your're starting a new project, you just need to run this :

npm install gulp one-gulp --save

This will install gulp and the one-gulp node module. If you don't have a gulpfile.js in your project, it will generate one with the minimum configuration.

init

If you're already using gulp, you need to install the one-gulp node module by running this :

npm install one-gulp --save

and then you'll be able to init one-gulp with this code :


var gulp = require('gulp'),
    one = require('one-gulp');

one.init(gulp, {
    // look at options documentation for details
});

The one.init() function adds several tasks to your gulp :

  • serve
  • watch
  • writeToDev
  • writeToProd
  • browserSync
  • graph

config options

src

tmp

dest

connectPort

browserSyncPort

bindHost

sortDeps // relative to src

Remote debugging

Using browser's tools

Chrome, Firefox, Opera and Safari provide remote debugging for their latest desktop and mobile browsers :

Using weinre

If you need to remote debug older versions of the above browsers, Internet Explorer or a WebView, you'll have to use weinre.

one-gulp uses BrowserSync, so weinre is already installed. You just need to add a target script in your pages and enable the debug interface.

Manual target script injection

If you want weinre to work, you can manually add a target script like this in your pages :

<script src="//[your-local-IP]:[options.weinrePort]/target/target-script-min.js#browsersync"></script>

Automatic target script injection

You can also set options.injectWeinreSnippet to true to automatically inject the weinre target script in your pages. This will only work on the BrowserSync port.

Enable the debugger

By default, after starting the servers, weinre is disabled. To enable it, just follow these two steps :

  1. Open http://[your-local-ip]:[browser-sync-conf-port]/remote-debug and enable Remote Debugger (weinre).
  2. Click on the Access remote debugger (opens in a new tab).