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

spark-build

v1.0.10

Published

Base build script including validation and test support

Downloads

20

Readme

SPARK Build

NOTE: The project is currently in beta state.

SPARK build provides aa set of common gulp tasks (etc. different gulp tasks) for building SPARK projects.

More Information & full documentation: http://www.k15t.com/display/SPARK

Installing

$ npm install spark-build

Usage

Basic usage as part of your project gulp file:

var sparkBuild = require('spark-build');

sparkBuild({
    moduleName: '<module-name>',
    resourcePath: '<resource-path>',
    paths: {
        'lib': {
            //The CSS files of the libraries
            'styles': {
                'prod': [],
                'dev':  []
            },
            'scripts': {
                //The js files of the libraries that should be delivered with the app (not minified!)
                'dev':  [],
                //The js files of the libraries that should be delivered with the app (minified!)
                'prod': [],
                //The js files of the libraries that must be provided to run tests
                'test': []
            },
            'assets':   []
        },
        'app': {
            'index': 'src/index.html',
            'styles':   [],
            'scripts':  [],
            'partials': [],
            'assets':   [],
            'tests':    [],
            'libs':     []
        }
    }
});

The configuration paths.app.libs is optional if you don't have multiple web applications in one project and no library you want to share between them, otherwise enter the path to the library you want to share. The whole directory will be copied to the current web application under app/libs.

After you added the required configuration you can start the gulp build as usual:

$ gulp default

or

$ gulp watch

Options

Following configurations can be customized as well if needed:

  • buildTargetDir (default '../../../../target')
  • karmaPort (default '9876')
  • karmaConfigFile (default configuration under build)
  • karmaConfigFileTemplate (default configuration under build)
  • jscsrc (Rule set to enforce best practices for java script, default configuration under build)

NOTE: The usage of Karam requires to add the desired dependencies to your project package.json!

Tips

The provided gulp task are split in different files according to what the task is intended for (e.g. cleanup.js, tests.js, ...).

This give you the opportunity to setup your own tasks based on the existing or in combination with your project specific gulp tasks.

License

Licensed under The MIT License (MIT).