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 🙏

© 2026 – Pkg Stats / Ryan Hefner

babel-jscs

v3.0.0-beta1

Published

**babel-jscs** allows you to lint **ALL** valid Babel code with [JSCS](https://github.com/jscs-dev/node-jscs). Big thanks to @sebmck!

Readme

babel-jscs Build Status

babel-jscs allows you to lint ALL valid Babel code with JSCS. Big thanks to @sebmck!

This package will be used in jscs itself. The recommended way to use it is to use use the esnext option.

Usage: jscs . --esnext or add "esnext": true to your .jscsrc

Also check out the fantastic babel-eslint to lint using ESLint.

NOTE: Please note that this is experimental and may have numerous bugs. It has been run against ember.js and babel-core with no errors (at the moment).

Known Issues

Issues

If there's an issue, first check if you can reproduce with the regular parser (esprima) and the latest version of jscs and babel-jscs.

Include: jscs and babel-jscs version, code snippet/screenshot

  • See if the issue is a duplicate.
  • Check if the issue is reproducible with regular jscs.
  • Run jscs in --verbose mode to get the rule name(s) that have issues.

How does it work?

JSCS allows custom parsers. This is great but some of the syntax nodes that Babel supports aren't supported by JSCS. When using this plugin, JSCS is monkeypatched and your code is transformed into code that JSCS can understand. All location info such as line numbers, columns is also retained so you can track down errors with ease.

Usage

Install

Since jscs 2.0 isn't released you will need to npm i jscs-dev/node-jscs#c5adeba

$ npm i -g jscs # global
$ npm i jscs # local

Setup

Example .jscsrc

{
  "esnext": true
}

Check out the JSCS docs for all possible rules.

Run

$ jscs your-files-here
# if you didn't add esnext to your config
$ jscs your-files-here --esnext