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

opine-scripts

v1.0.0

Published

A module to compile javascript with browserify

Downloads

58

Readme

opine-scripts

This module compiles javascript through browserify.

Installation:

yarn add gulp gulp-opine opine-scripts

Configuration:

Reminder: with opine you can run gulp config-defaults to print out the current values of all configuration values that haven't been explicitly defined.

  • opine.scripts.source: the directory containing the entry file. Any file being changed in this directory or its children will trigger a rebuild.
  • opine.scripts.entry: the name of the entry file.
  • opine.scripts.dest: the directory to save the output .js file
  • opine.scripts.target: the filename of the compiled .js file in the destination directory

Note that the filesystem watch functionality just monitors for any modification of any file in the source tree rather than intelligently monitoring files that have been required. Originally this module was written to use watchify but we encountered issues with linux incompatibility and decided to switch this module over to use the same watch as the rest of the opine ecosystem.

Multiple entry points and targets

The basic setup above accounts for a single entry point that bundles down to a single script. If you need multiple entry points, the following configuration will override the entry and target configuration values.

opine: {
    scripts: {
        multibundle: [ 
            { entry: 'form-entry.js', target: 'forms.js' },
            'main.js'   // equivalent to { entry: 'main.js', target: 'main.js' }
        ]
    }
}

Babelify

If you want to apply Babelify transforms, configure opine.scripts.transforms to be an array of the names of the presets you want to apply.

opine: {
    scripts: {
        transforms: ['es2015']
    }
}

Note that Babelify and its presets are NOT included as dependencies of opine-scripts; you will need to install them yourself (for the example above, you'd need to add the babelify and babel-preset-es2015 packages to your project).