All Projects → strvcom → eslint-config-javascript

strvcom / eslint-config-javascript

Licence: BSD-3-Clause license
Write bulletproof JavaScript like a pro! 😎

Programming Languages

javascript
184084 projects - #8 most used programming language
shell
77523 projects

Projects that are alternatives of or similar to eslint-config-javascript

verilog-coding-style
Verilog (SystemVerilog) coding style
Stars: ✭ 36 (+5.88%)
Mutual labels:  coding-standards, coding-style
XS-Labs-Style-Guide
XS-Labs Coding Style Guide for C, C++, Objective-C and x86 Assembly
Stars: ✭ 20 (-41.18%)
Mutual labels:  coding-standards, coding-style
codingstyle
Java coding style and template project used at Munich university of applied sciences
Stars: ✭ 19 (-44.12%)
Mutual labels:  coding-standards, coding-style
phpcs-psr4-sniff
[READ-ONLY] PHP_CodeSniffer sniff that checks class name matches PSR-4 project structure.
Stars: ✭ 23 (-32.35%)
Mutual labels:  coding-standards, coding-style
OpenStaticAnalyzer
OpenStaticAnalyzer is a source code analyzer tool, which can perform deep static analysis of the source code of complex systems.
Stars: ✭ 19 (-44.12%)
Mutual labels:  coding-standards, coding-style
Coding-Standards
Coding Guidelines for C#
Stars: ✭ 125 (+267.65%)
Mutual labels:  coding-standards, coding-style
Codor
Custom PHPCS sniffs to find Code Smells
Stars: ✭ 40 (+17.65%)
Mutual labels:  coding-standards, coding-style
cscs
A curated list of Coding Style Conventions and Standards.
Stars: ✭ 1,486 (+4270.59%)
Mutual labels:  coding-standards, coding-style
eslint-config
MOXY eslint configuration to be used across several JavaScript projects
Stars: ✭ 14 (-58.82%)
Mutual labels:  coding-standards, coding-style
sniff
Simpler PHP code sniffer built on top of PHP-CS-Fixer.
Stars: ✭ 14 (-58.82%)
Mutual labels:  coding-standards
development-best-practices
程序员开发规范,其中包括Java、JavaScript、CSS、Oracle、MySQL的开发编码规范和规约
Stars: ✭ 14 (-58.82%)
Mutual labels:  coding-standards
coding-standard
Consistence - Coding Standard - PHP Code Sniffer rules
Stars: ✭ 73 (+114.71%)
Mutual labels:  coding-standards
grunt-stylelint
Stylelint adapter for the Grunt task runner.
Stars: ✭ 26 (-23.53%)
Mutual labels:  coding-standards
Twig-CS-Fixer
A tool to automatically fix Twig Coding Standards issues
Stars: ✭ 61 (+79.41%)
Mutual labels:  coding-standards
Php codesniffer
PHP_CodeSniffer is a set of two PHP scripts; the main phpcs script that tokenizes PHP, JavaScript and CSS files to detect violations of a defined coding standard, and a second phpcbf script to automatically correct coding standard violations. PHP_CodeSniffer is an essential development tool that ensures your code remains clean and consistent.
Stars: ✭ 9,004 (+26382.35%)
Mutual labels:  coding-standards
symfony-custom-coding-standard
Customized Symfony coding standard
Stars: ✭ 13 (-61.76%)
Mutual labels:  coding-standards
wptide
🌊 Tide is a series of automated tests run against every WordPress.org theme and plugin
Stars: ✭ 77 (+126.47%)
Mutual labels:  coding-standards
eslint-config-naver
Naver JavaScript Coding Conventions rules for eslint
Stars: ✭ 184 (+441.18%)
Mutual labels:  coding-standards
php-cs-fixer-extensions
PHP-CS-Fixer extensions and configurations
Stars: ✭ 71 (+108.82%)
Mutual labels:  coding-standards
sprint tutorial
Tutorial and mock repository to teach people to contribute to open source
Stars: ✭ 18 (-47.06%)
Mutual labels:  coding-standards

JavaScript Coding Standards

DEPRECATED: This project has been deprecated in favour of a more granular variant hosted over at @strvcom/code-quality-tools.

See migrating.md for help in moving over to the new ESLint-specific rulesets.


Build Status ESLint version

About

This repository contains various configuration files for the awesome JavaScript linter, ESLint. The configuration files are purposefully separated into various categories to allow their composition according to developers' preferences or requirements. It should also make adoption of ESLint across existing codebases easier.

Usage

Installation

This package can be installed via npm (make sure you also install the latest version of ESLint):

npm install --save-dev eslint@latest @strv/eslint-config-javascript@latest

Configuration

Once the ruleset is installed, you must create your own .eslintrc.{js,json,yml} configuration file in your project's root (or in some of the subfolders, if you want to apply different rules to different parts of your code) and include those rulesets that you want to use. See the tutorial directory for, well... tutorial.

Integrating ESLint with your IDE/editor

See the editor-integrations document for tips.

Example configuration files

See the tutorial directory for lots of example config files.

Available rulesets

For Node.js

  • @strv/javascript/environments/nodejs/v10
  • @strv/javascript/environments/nodejs/v8-3
  • @strv/javascript/environments/nodejs/v8
  • @strv/javascript/environments/nodejs/v6
  • @strv/javascript/environments/nodejs/optional

For React

  • @strv/javascript/environments/react/v16
  • @strv/javascript/environments/react/v15
  • @strv/javascript/environments/react/optional
  • @strv/javascript/environments/react/accessibility

    This one contains rules specific to web accessibility best practices.

For Flow

  • @strv/javascript/environments/flow/recommended

For TypeScript

Requires configuration. See the docs for more info.

  • @strv/javascript/environments/typescript/recommended

For Mocha

  • @strv/javascript/environments/mocha/recommended

Coding styles

These rulesets include rules which deal with how the code looks like and not how it works. They help keep the code clean and consistent.

  • @strv/javascript/coding-styles/recommended

  • @strv/javascript/coding-styles/fixable

    This is a subset of the recommended coding style ruleset and includes only rules which ESLint can fix automatically. This is great for gradual adoption of coding style rulesets into existing projects.

  • @strv/javascript/coding-styles/flow

    This one contains coding style rules for code using Flow

License

This software is licensed under the BSD-3-Clause License. See the LICENSE file for more information.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].