We have collection of more than 1 Million open source products ranging from Enterprise product to
small libraries in all platforms. We aggregate information from all open source repositories.
Search and find the best for your needs. Check out projects section.
This is a guide for writing consistent and aesthetically pleasing node.js code. It is inspired by what is popular within the community, and flavored with some personal opinions.There is a .jshintrc which enforces these rules as closely as possible. You can either use that and adjust it, or use this script to make your own.
Shareable configs are designed to work with the extends feature of .eslintrc files. You can learn more about Shareable Configs on the official ESLint website.Note: We omitted the eslint-config- prefix since it is automatically assumed by ESLint.
Build consistent and versioned styleguides by including and running consistent lint files across projects.Your styleguide should be verisoned and consistent across all of your projects. This means that you should only have ONE .jshintrc and/or .jscsrc file anywhere. But how can this be accomplished easily? By making your own styleguide using fashion-show.
This package (standard-react) is DEPRECATED. Supporting standard already takes a ton of time. Supporting a fork isn't worth the effort, especially since this gets less than 200 downloads per month, half of which are probably bots. There are only a handful of extra rules this package provides anyway...v3.0.0 will be the last version of this package. It corresponds to the v8.0.0 release of standard.
Issues regarding rules should be reported on the ESLint issue tracker as it's the actual linter.This option instructs ESLint to try to fix as many issues as possible. The fixes are applied to the gulp stream. The fixed content can be saved to file using gulp.dest (See example/fix.js). Rules that are fixable can be found in ESLint's rules list.