![]() ![]() Open the command palette ( Ctrl / Cmd + Shift + P) and select ESLint: Manage Library Execution to open the dialog for your project and confirm with 'Accept'.ĭid you maybe disable the rule you're testing? The ESLint plugin requires permission to execute the local ESLint installation from your node_modules. Make sure, the ESLint plugin is installed and also enabled in VSCode. Maybe you've just set up a new VSCode installation or something's gone wrong syncing your settings. Learn more about Configuration Cascading and Hierarchy in the official documentation.ĭo you have the ESLint plugin installed and enabled in VSCode? Use ls -a to show hidden files in your terminal.Īdditionally, you can stop ESLint from searching further up the directory tree by adding the root option to the. eslintrc files, remember, that they might be invisible to your file explorer. Sometimes, I accidentally scaffold a project in my home directory and forget to delete the hidden. Make sure you don't have any additional configuration files anywhere in your project or in the directories above, that you are unaware of. eslintrc configuration files automatically extend configuration files in higher directories, this can cause weird issues. In case you're using TypeScript, Vue.js or other non-standard JavaScript files, make sure to tell ESLint about your file extensions by using the -ext flag like so -ext. This was not easily detected, since ESLint didn't throw any warning but just quit silently.ĭid you make sure, ESLint is linting the correct file extensions? ![]() I recently encountered a project where the lint script in the package.json was missing the dot at the very end which tells ESLint to start linting in the same directory as the configuration file is in. Enter fullscreen mode Exit fullscreen modeĭid you tell ESLint, which directory to lint? ![]()
0 Comments
Leave a Reply. |