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

gulp-scripts-index

v0.3.0

Published

Input html file(s) and get a stream of all referenced scripts which can then be usedfor further processing like concatenation, minification or for testing

Downloads

25

Readme

gulp-scripts-index NPM version Build Status Dependency Status Coverage percentage

Input html file(s) and get a (ordered) stream of all referenced scripts which can then be used for further processing, like concatenation, minification or for testing

Install

$ npm install --save-dev gulp-scripts-index

Usage

Simple Example

If you simply need all files that are referenced in the index.html and you don't want to use the excellent useref for further processing it is as simple as:

var gsi = require('gulp-scripts-index');

gulp.src(['index.html'])
	.pipe(gsi())
	.pipe(doSomethingElse())
	.pipe(gulp.dest('./'))

Example Usage with Karma

It can be tedious to configure Karma with all required source files to run tests - in particular, when this information is already known, e.g. because all the script files are referenced in the index.html. In this case, it is quite easy to use gulp-scripts-index to parse the index.html and feed all required scripts to karma. For more information on running karma with gulp, please also refer to karma-runner/gulp-karma

var gsi = require('gulp-scripts-index');
// we will use the gutils to buffer all piped script files and output them as an array
var gutils = require('gulp-utils');
// obviously, we'll also need karma
var karma = require('karma.runner').server;

/**
 * Run test once and exit
 */
gulp.task('test', function (done) {
	gulp.src(['index.html'])
    .pipe(gsi({
        IE: false
    }))
    .pipe(gutil.buffer(function(err, files) {
      // files now contains a list of all references scripts in the index.html - in the right order to kick right off. However, it is still a list of vinyl file objects
      // let's reduce it to an array of strings
      files = files.map(function(file){return file.relative;})
      karma.start({
        configFile: __dirname + '/karma.conf.js',
        // pass in our detected script files - of course you will have to add your actual tests and / or mocks
        files: files.concat(['tests/unit/**.js', 'tests/mocks/**.js']),
        singleRun: true
      }, done);
    });
});

Options

  • IE {Boolean} - Defaults to false. Whether or not to also include scripts that are for IE only, i.e. they are surrounded by Conditional comments like so:
<script src="main.js"></script>
<!--[if IE 9]>
	<script src="ie-specific.js"></script>
<![endif]-->

In the example above, if IE is set to true, the plugin will also pipe the ie-specific.js in addition to the main.js.

  • searchPaths {Array} - Defaults to []. this option can be used to specify additional locations in which to look for the script files referenced in index.html. That way, even files that are not stored at the actually specified location can be found and processed. The specified searchpaths are to be defined as relative to the process's cwd.

License

MIT © Benedikt Reiser