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

jarvis-es5

v1.1.0

Published

Complete gulp task for compiling js with gelp of webpack

Downloads

3

Readme

jarvis-js

Complete gulp task for compiling js, with help of webpack.

NPM

Installation

npm i --save-dev jarvis-es5

Usage

I tried to do usage of this task as simple as posible. The following example will compile all the *.entry.js files under the folder src/ into to destination folder dist/, and rename it all from *.entry.js to *.bundle.js

const gulp = require('gulp');
var js = require('./index');

var jsConfig = {
    entry: 'test/src/**/*.entry.js',
    output: 'test/dist/js/',
    webpack: require('./test/webpack.config.js')
};

gulp.task('js:build', (done) => {
    jsConfig.webpack.watch = false;
    return js.run(jsConfig)(done);
});

gulp.task('js:watch', (done) => {
    jsConfig.webpack.watch = true;
    return js.run(jsConfig)(done);
});

So we had the folowing file tree:

 src/
     main.entry.js
     common.entry.js

after running less:build (or less:watch if you want to watching changes), we will have:

 src/
     main.entry.js
     common.entry.js
 dist/
     main.bundle.js
     common.bundle.js

Webpack

As you can see, I use webpack for bundling js, it means you can use all power of webpack.config.js (except entry and output options).

Jarvis

But the killer-feature of this task is gulp-jarvis. With help of this plugin we can easily redeclare the destination folder by adding a special comment file to the beginning of the entry file. So let's go back to the previous example:

 src/
     main.entry.js
     common.entry.js

Lets change the contents of the file style.entry.less a little bit. We will add the following line to the beginning of style.entry.less /*file-output:dist/js/main.js;*/

And after this ша run less:build again at the output we will have:

 src/
     main.entry.less
     common.entry.less
 dist/
     common.bundle.css
     style/
         main.js
         

See, its so easy.

Options

The API of the package has only one method:

js.build(options)
defaultOptions = {
    entry: `src/**/*.entry.js`, // source glob for gulp.src(...)
    output: 'dist/js/', //default destination folder
    webpack: undefined, //webpack config
}