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

modern-standard

v1.4.3

Published

A linter based on standard, built with a modern ruleset.

Downloads

12

Readme

JavaScript Modern Standard Style

travis

One Style to Rule Them All

No decisions to make. No .eslintrc, .jshintrc, or .jscsrc files to manage. It just works.

This module saves you (and others!) time in two ways:

  • No configuration. The easiest way to enforce consistent style in your project. Just drop it in.
  • Catch style errors before they're submitted in PRs. Saves precious code review time by eliminating back-and-forth between maintainer and contributor.

This is a linter for the future, based on the standard linter. It expects to be run within a babel environment, using the latest available babel syntax.

Rule Differences from Standard

Methodology Differences from Standard

  • We will freely update rules based on current best practices. Becuase of this we recommend that you lock down the current version of modern-standard.
  • We are currently only targeting the latest javascript syntax, generally this code is transpiled by babel.
  • We want to move faster and be more receptive to community issues and contributions.
  • Everything is under one organization, and all linting code is in a single repo. This makes it much easier for contributors.
  • This is an experiment and we're happy if standard adopts these rules or if this repository is forked.

Install

npm install modern-standard

Integrating modern-standard

  1. Add it to package.json
{
  "name": "my-package",
  "devDependencies": {
    "modern-standard": "*"
  },
  "scripts": {
    "test": "modern-standard && node my-tests.js"
  }
}
  1. Check style automatically when you run npm test
$ npm test
Error: Use JavaScript Modern Standard Style
  lib/torrent.js:950:11: Expected '===' and instead saw '=='.
  1. Never give style feedback on a pull request again!

Text editor plugins

First, install modern-standard. Then, install the appropriate plugin for your editor:

Sublime Text

SublimeLinter-contrib-modern-standard is currently under construction and should be published in package control soon.

Atom

ide-plugin-atom can be found here: https://atom.io/packages/modern-standard-ide-plugin-atom