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

spasdk

v1.2.1

Published

SPA development environment and tools.

Downloads

15

Readme

Development tasks

build status npm version dependencies status devDependencies status Gitter

Installation

npm install spasdk

Usage

Add to the scope:

var spasdk = require('spasdk');

Environment variables

Name | Description -----------|------------- PATH_ROOT | read-only absolute path to main application directory (where package.json is located) PATH_APP | relative to PATH_ROOT directory with files ready to be deployed PATH_SRC | relative to PATH_ROOT directory with source files to generate development and release application files PATH_CFG | relative to PATH_ROOT directory with configuration files for tasks and application itself PACKAGE | read-only absolute path to the application package.json file

Some to these variables can be redefined in run-time:

PATH_CFG=some_other_dir gulp

Application configuration

The directory contains all application configuration files.

File gulp.js can redefine default configuration options for all gulp tasks.

For example:

module.exports = {
    default: {
        notifications: {
            popup: {
                fail: false
            }
        }
    },
    jade: {
        default: {
            source: 'sources/pug/main.pug'
        },
        develop: {
            target: 'dst/debug.html'
        },
        release: false,
        test: {}
    },
    sass: false
};

This will apply the following changes:

  • disable failure popup notifications for all profiles and all tasks
  • set sources/pug/main.pug as the main entry point (instead of default src/jade/main.jade) for all Jade profiles
  • set dst/debug.html as the intended output file (instead of default app/develop.html) for Jade develop profile only
  • remove Jade release profile
  • add new Jade test profile filled with options from default profile
  • completely disable all SASS tasks

To make sure all options are correct it's possible to print the current config set:

gulp jade:config

Contribution

If you have any problem or suggestion please open an issue here. Pull requests are welcomed with respect to the JavaScript Code Style.

License

spasdk is released under the GPL-3.0 License.