idea folder where PhpStorm-specific project metadata is stored). Paths relative to the project base directory (the parent folder of the. If the auto-detected working directory doesn't match your project configuration, you need to specify the working directory (directories) manually. eslintrc.* file, or a package.json file with either a eslintIgnore or a eslintConfig property. First it looks for a directory closest to the linted file which contains a. In the Working directories field, specify the working directories for the ESLint process.īy default the field is empty and PhpStorm detects the working directory automatically. In the ESLint package field, specify the location of the eslint or standard package. In the Settings dialog ( Ctrl+Alt+S), go to Languages & Frameworks | JavaScript | Code Quality Tools | ESLint, and select Manual ESLint configuration. With manual configuration, you can use a custom ESLint package, configuration file, and working directories, as well as apply various additional rules and options. To configure ESLint automatically in all new projects, open the Settings for New Projects dialog ( File | New Projects Setup | Settings for New Projects), go to Languages & Frameworks | JavaScript | Code Quality Tools | ESLint, and select the Automatic ESLint configuration option. To configure ESLint automatically in the current project, open the Settings dialog ( Ctrl+Alt+S), go to Languages & Frameworks | JavaScript | Code Quality Tools | ESLint, and select the Automatic ESLint configuration option. This lets you apply a specific ESLint version or a specific set of plugins to each path in a monorepo or a project with multiple ESLint configurations. If you have several package.json files with ESLint listed as a dependency, PhpStorm starts a separate process for each package.json and processes everything below it. eslintrc.* is found in the current file folder, PhpStorm will look for one in its parent folders up to the project root. eslintrc.* configuration file from the folder where the current file is stored. With automatic configuration, PhpStorm uses the ESLint package from the project node_modules folder and the. You can choose to configure it automatically or specify all the configuration settings manually. Optionally, install additional plugins, for example, eslint-plugin-react to lint React applications.Īctivate and configure ESLint in PhpStormīy default, ESLint is disabled. Npm install -save-dev eslint to install ESLint as a development dependency. Npm install -g eslint for global installation. In the embedded Terminal ( Alt+F12), type one of the following commands: Before you startĬonfigure a Node.js interpreter in your project as described in Configuring a local Node.js interpreter, or in Using Node.js on Windows Subsystem for Linux, or in Configuring remote Node.js interpreters. With ESLint, you can also use JavaScript Standard Style as well as lint your TypeScript code.īesides JavaScript and TypeScript, ESLint can be applied to files of other types in the entire project or in its specific parts, see Configure linting scope. PhpStorm shows warnings and errors reported by ESLint right in the editor, as you type. PhpStorm integrates with ESLint which brings a wide range of linting rules that can also be extended with plugins.
0 Comments
Leave a Reply. |