node-jscs - :arrow_heading_up: JavaScript Code Style checker (unmaintained)

  •        6

:arrow_heading_up: JavaScript Code Style checker (unmaintained)

http://jscs.info
https://github.com/jscs-dev/node-jscs

Dependencies:

chalk : ~1.1.0
cli-table : ~0.3.1
commander : ~2.9.0
cst : ^0.4.3
estraverse : ^4.1.0
exit : ~0.1.2
glob : ^5.0.1
htmlparser2 : 3.8.3
js-yaml : ~3.4.0
jscs-jsdoc : ^2.0.0
jscs-preset-wikimedia : ~1.0.0
jsonlint : ~1.6.2
lodash : ~3.10.0
minimatch : ~3.0.0
natural-compare : ~1.2.2
pathval : ~0.1.1
prompt : ~0.2.14
reserved-words : ^0.1.1
resolve : ^1.1.6
strip-bom : ^2.0.0
strip-json-comments : ~1.0.2
to-double-quotes : ^2.0.0
to-single-quotes : ^2.0.0
vow : ~0.4.8
vow-fs : ~0.3.4
xmlbuilder : ^3.1.0

Tags
Implementation
License
Platform

   




Related Projects

gulp-jscs - Check JavaScript code style with jscs

  •    Javascript

Issues with the output should be reported on the JSCS issue tracker. JSCS config should be placed in a .jscsrc file.


grunt-jscs - Grunt task for JSCS

  •    Javascript

Task for checking JavaScript Code Style with jscs. Run this task with the grunt jscs command.

polyjuice - A utility to convert JSHint and JSCS files into ESLint files and vice-versa

  •    Javascript

Polyjuice is a utility that converts JSHint and JSCS files into ESLint files and the other way around. When using polyjuice.from.eslint an object with keys jscs and jshint is returned.

gts - ☂️ TypeScript style guide, formatter, and linter.

  •    TypeScript

NOTE: THIS README refers to the master branch which corresponds to the upcoming 1.0 release. To view documentation for the currently released version of this module see: https://github.com/google/gts/tree/v0.9.x. gts is Google's TypeScript style guide, and the configuration for our formatter, linter, and automatic code fixer. No lint rules to edit, no configuration to update, no more bike shedding over syntax.

esformatter - ECMAScript code beautifier/formatter

  •    Javascript

ECMAScript code beautifier/formatter.This tool is still missing support for many important features. Please report any bugs you find, the code is only as good as the test cases. Feature requests are very welcome.

atom-beautify - :lipstick: Universal beautification package for Atom editor (:warning: Currently migrating to https://github

  •    CoffeeScript

Atom-Beautify respects the core.telemetryConsent configuration option from Atom editor. If you do not wish to have usage data sent to Google Analytics then please set core.telemetryConsent to no or undecided option before using Atom-Beautify. See Anonymous Analytics section of docs for details. Thank you. Atom-Beautify is going to be completely rewritten with Unibeautify at its core! See unibeautify branch for work in progress and Issue #1174.

puppet-lint - Check that your Puppet manifests conform to the style guide

  •    Ruby

Puppet Lint tests Puppet code against the recommended Puppet language style guide. Puppet Lint validates only code style; it does not validate syntax. To test syntax, use Puppet's puppet parser validate command. Puppet Lint version 2 is the last planned version with support for Puppet 3 and Ruby 1.8.7. The next major version of Puppet Lint will drop support for these versions.

rubocop - A Ruby static code analyzer and formatter, based on the community Ruby style guide.

  •    Ruby

RuboCop is a Ruby static code analyzer and code formatter. Out of the box it will enforce many of the guidelines outlined in the community Ruby Style Guide. RuboCop is extremely flexible and most aspects of its behavior can be tweaked via various configuration options.

yapf - A formatter for Python files

  •    Python

Most of the current formatters for Python --- e.g., autopep8, and pep8ify --- are made to remove lint errors from code. This has some obvious limitations. For instance, code that conforms to the PEP 8 guidelines may not be reformatted. But it doesn't mean that the code looks good.YAPF takes a different approach. It's based off of 'clang-format', developed by Daniel Jasper. In essence, the algorithm takes the code and reformats it to the best formatting that conforms to the style guide, even if the original code didn't violate the style guide. The idea is also similar to the 'gofmt' tool for the Go programming language: end all holy wars about formatting - if the whole codebase of a project is simply piped through YAPF whenever modifications are made, the style remains consistent throughout the project and there's no point arguing about style in every code review.

lint-staged - 🚫💩 — Run linters on git staged files

  •    Javascript

Linting makes more sense when running before committing your code. By doing that you can ensure no errors are going into repository and enforce code style. But running a lint process on a whole project is slow and linting results can be irrelevant. Ultimately you only want to lint files that will be committed. This project contains a script that will run arbitrary npm and shell tasks with a list of staged files as an argument, filtered by a specified glob pattern.

javascript - JavaScript Style Guide

  •    Javascript

Note: this guide assumes you are using Babel, and requires that you use babel-preset-airbnb or the equivalent. It also assumes you are installing shims/polyfills in your app, with airbnb-browser-shims or the equivalent.1.1 Primitives: When you access a primitive type you work directly on its value.

Solium - Linter to identify and fix style & security issues in Solidity

  •    Javascript

Solium analyzes your Solidity code for style & security issues and fixes them. To know which lint rules Solium applies for you, see Style rules and Security rules.