Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

w12t-standard

Package Overview
Dependencies
Maintainers
1
Versions
1
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

w12t-standard

Webkollektivet standard

  • 12.0.0
  • latest
  • Source
  • npm
  • Socket score

Version published
Weekly downloads
0
decreased by-100%
Maintainers
1
Weekly downloads
 
Created
Source

JavaScript Standard Style

All the goodness of [standard/standard] with Webkollektivet's preferences sprinkled on top.

Install

npm install w12t-standard

Rules

Importantly:

  • Semicolons
  • Multiline comma dangle
  • JSX double quotes
  • Check [standard/standard] for the rest of the rules.

Usage

The easiest way to use JavaScript Standard Style to check your code is to install it globally as a Node command line program. To do so, simply run the following command in your terminal:

npm install w12t-standard -g

After you've done that you should be able to use the w12t-standard program. The simplest use case would be checking the style of all JavaScript files in the current working directory:

$ w12t-standard
Error: Use JavaScript Standard Style
  lib/torrent.js:950:11: Expected '===' and instead saw '=='.

Editor plugins

  • Atom users - Install linter-js-standard-engine

Specify what linter to use using by setting standard-engine in your package.json file:

{
  "standard-engine": "w12t-standard"
}

What you might do if you're clever

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

Custom Parser

To use a custom parser, install it from npm (example: npm install babel-eslint) and add this to your package.json:

{
  "w12t-standard": {
    "parser": "babel-eslint"
  }
}

Ignoring files

Just like in standard, The paths node_modules/**, *.min.js, bundle.js, coverage/**, hidden files/folders (beginning with .), and all patterns in a project's root .gitignore file are automatically excluded when looking for .js files to check.

Sometimes you need to ignore additional folders or specific minfied files. To do that, add a w12t-standard.ignore property to package.json:

"w12t-standard": {
  "ignore": [
    "**/out/",
    "/lib/select2/",
    "tmp.js"
  ]
}

Make it look snazzy

If you want prettier output, just install the snazzy package and pipe w12t-standard to it:

$ w12t-standard --verbose | snazzy

See [standard/standard] for more information.

Keywords

FAQs

Package last updated on 10 Feb 2018

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc