From cc383057a30d988bf21336a4f9cbc1d34808b0ae Mon Sep 17 00:00:00 2001 From: Enguerrand de Ribaucourt Date: Fri, 20 Sep 2024 09:55:46 +0200 Subject: [PATCH] Dev: Use local eslint in vscode The live linter must be configured to use our version of eslint and plugins. Otherwise, a global install would be needed. --- .vscode/settings.json | 3 ++- README-DEVELOPER.md | 6 +----- 2 files changed, 3 insertions(+), 6 deletions(-) diff --git a/.vscode/settings.json b/.vscode/settings.json index 6808821e..1c0ad9bf 100644 --- a/.vscode/settings.json +++ b/.vscode/settings.json @@ -14,5 +14,6 @@ "source.fixAll.eslint": "explicit" }, "jest.jestCommandLine": "node_modules/.bin/jest", - "jest.monitorLongRun": 300000 + "jest.monitorLongRun": 300000, + "eslint.nodePath": "${workspaceFolder}/node_modules", } diff --git a/README-DEVELOPER.md b/README-DEVELOPER.md index 9466b893..781ffa24 100644 --- a/README-DEVELOPER.md +++ b/README-DEVELOPER.md @@ -67,11 +67,7 @@ One can check coding style using ``` sh npm run lint ``` -Install the recommended extensions to automatically fix linting errors through VSCode. -You will also need to install the `eslint` dependencies globally: -``` sh -npm install -g eslint typescript-eslint -``` +Install the recommended extensions to automatically fix linting errors when possible. ### Unit tests