We may make changes to core rules to better work with language extensions (such as JSX, Flow, and TypeScript) on a case-by-case basis. We will make changes to core rules in order to avoid crashes on stage 3 ECMAScript syntax proposals (as long as they are implemented using the correct experimental ESTree syntax). What about experimental features?ĮSLint's parser only officially supports the latest final ECMAScript standard. You can set your desired ECMAScript syntax (and other settings, like global variables or your target environments) through configuration. We recommend using eslint-plugin-react if you are using React and want React semantics. React applies specific semantics to JSX syntax that ESLint doesn't recognize. Please note that supporting JSX syntax is not the same as supporting React. Yes, ESLint natively supports parsing JSX syntax (this must be enabled in configuration). You can use npm view eslint-plugin-myplugin peerDependencies to see what peer dependencies eslint-plugin-myplugin has. Make sure your plugins' peerDependencies have been installed as well.Make sure you have run npm install and all your dependencies are installed.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).Using both tools is common, refer to Prettier's documentation to learn how to configure them to work well with each other. No, ESLint and Prettier have diffent jobs: ESLint is a linter (looking for problematic patterns) and Prettier is a code formatter. 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |