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-init-block

v0.2.0

Published

Generates css file structure according to classes used in HTML. Relies on BEM naming for classes.

Downloads

3

Readme

grunt-init-block

Generates css file structure according to classes used in HTML. Relies on BEM naming for classes.

Getting Started

This plugin requires Grunt ~0.4.1

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-init-block --save-dev

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

grunt.loadNpmTasks('grunt-init-block');

The "initBlock" task

Overview

In your project's Gruntfile, add a section named initBlock to the data object passed into grunt.initConfig().

grunt.initConfig({
	initBlock: {
		options: {
			// Task-specific options go here.
		},
		your_target: {
			// Target-specific file lists and/or options go here.
		}
	}
})

Options

options.attr

Type: String Default value: 'init-in'

Attribute that contains the name of the target file. Example: <div class="block" init-in="blocks.css">

options.element

Type: String Default value: '__'

Element class name separator in your HTML. Example: <div class="block__element">

options.modifier

Type: String Default value: '_'

Modifier class name separator in your HTML. Example: <div class="block block_modifier">

options.shortModifier

Type: Boolean Default value: true

Use a short modifier. Example: <div class="block _modifier">

options.preprocessor

Type: Boolean Default value: false

Use stylus style for output without braces.

options.indentChar

Type: String Default value: '\t'

Output line indent style. Use spaces or tabs.

options.indentSize

Type: Number Default value: 1

Output line indent style. How much should be char repeated.

Usage Example

Describe the task in your Gruntfile.js:

grunt.initConfig({
	initBlock: {
		options: {},
		all: {
			src: ['test/*.html'],
            dest: 'test/'
		}
	}
})

write html:

<div class="post _modifier" init-in="blocks.css">
	<h2 class="post__title"></h2>
	<div class="post__content"></div>
	<div class="post__comments"></div>
</div>

then run grunt initBlock and you will get in blocks.css:

.post {

}
	.post__title {

	}
	.post__content {

	}
	.post__comments {

	}
.post._modifier {

}

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.