Make sure your plugins (and ESLint) are both in your project's package.json as devDependencies (or dependencies, if your project uses ESLint at runtime).You can use ESLint for everything, or you can combine both using Prettier to format your code and ESLint to catch possible errors. No, ESLint does both traditional linting (looking for problematic patterns) and style checking (enforcement of conventions). If you try ESLint and believe we are not yet compatible with a JSCS rule/configuration, please create an issue (mentioning that it is a JSCS compatibility issue) and we will evaluate it as per our normal process. We are now at or near 100% compatibility with JSCS. We have prepared a migration guide to help you convert your JSCS settings to an ESLint configuration. JSCS has reached end of life and is no longer supported. Filing Issuesīefore filing an issue, please be sure to read the guidelines for what you're reporting:įrequently Asked Questions I'm using JSCS, should I migrate to ESLint?
Code of ConductĮSLint adheres to the JS Foundation Code of Conduct. The three error levels allow you fine-grained control over how ESLint applies rules (for more configuration options and details, see the configuration docs). "error" or 2 - turn the rule on as an error (exit code will be 1)."warn" or 1 - turn the rule on as a warning (doesn't affect exit code).The first value is the error level of the rule and can be one of these values: The names "semi" and "quotes" are the names of rules in ESLint.
0 kommentar(er)
