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

grunt-kss-node

v1.0.4

Published

KSS styleguide generator for grunt.

Downloads

11

Readme

grunt-kss-node

NPM version Dependency Status Built with Grunt

Npm Downloads

KSS styleguide generator for grunt.

Getting Started

This plugin requires Grunt ~0.4.x

If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

npm install grunt-kss --save-dev

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

grunt.loadNpmTasks('grunt-kss');

The "kss" config and an example task

Overview

To set up the kss config, add a section named kss to the data object passed into grunt.initConfig(), in your project's Gruntfile.

grunt.initConfig({
  kss: {
    options: {
      css: '/path/to/style.css',
    },
    dist: {
	    files: {
	      '/path/to/destdir': ['/path/to/sourcedir']
	    }
  	}
  }
});

Then, once you've added the config information above, you can add the kss build step to an existing task (not shown) or can create your own task. Here is an example task that you can create:

grunt.registerTask('styleguide', [
  // Add other tasks here if needed
  'kss'
  // Add other tasks here if needed
]);

Finally, you can call kss by running grunt styleguide.

Options

options.template

Type: String Default value: null

A string value that is used to use a custom template to build your styleguide.

options.helpers

Type: String Default value: null

Specify the location of custom handlebars helpers; see http://bit.ly/kss-helpers

options.mask

Type: String Default value: null

A string value that is used to use a custom mask for detecting stylesheets.

options.custom

Type: String Default value: null

A string value that is used to use a custom property name when parsing KSS comments.

options.css

Type: String Default value: null

A string value that is used to use including a CSS stylesheet for your styleguide.

options.js

Type: String Default value: null

A string value that is used to use including a JavaScript file for your styleguide.

options.config

Type: String Default value: null

Load the kss-node configuration from a JSON file

Contributing

In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code using Grunt.