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 🙏

© 2025 – Pkg Stats / Ryan Hefner

jscs-bem

v0.2.0

Published

jscs bem plugin

Readme

jscs-bem

Plugin for jscs with bem code style preset.

What is it?

A preset library for jscs (code-style linter) with examples and bem-specific code-style checks.

Presets inside

Usage

To use it you need fresh jscs, and simple .jscsrc file in your project root.

Run in your project root to quick start:

npm i jscs jscs-bem --save-dev
echo '{ plugins: ["jscs-bem"], preset: "bem" }' > .jscsrc

Contribution

  1. File an issue with properly described suggestion or problem;
  2. Decide which presets or rules your issue affects;
  3. Create a feature-branch with an issue number (issues/<issue_number>). E.g. for an issue 42 it will looks like issues/42;
  4. Commit changes with a proper message, e.g.:
<preset>: <short description>

[<full description if needed>]

Fixes #<issue_number>
[Ref #<referenced issue/pr>]
  1. Push and make a pull-request from your feature-branch.
  2. Link your pull request with an issue number any way you like (if you forget to do it in commit message). A comment will work perfectly.
  3. Wait for your pull request and the issue to be closed ;-)

Licence

Code and documentation copyright 2015 YANDEX LLC. Code released under the Mozilla Public License 2.0.