From fc7aa003cd41b84eb1e7826d36d41ea5258aa57e Mon Sep 17 00:00:00 2001 From: Karl Horky Date: Thu, 16 Oct 2025 12:26:36 +0200 Subject: [PATCH 1/3] Configure shell env timeout to avoid PATH problems on VS Code update --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 956c84da..3d2cf397 100644 --- a/README.md +++ b/README.md @@ -322,7 +322,7 @@ This extension contributes the following variables to the [settings](https://cod - `eslint.useESLintClass` (@since 2.2.0) - whether to use the ESLint class API even if the CLIEngine API is present. The setting is only honor when using ESLint version 7.x. - `eslint.run` - run the linter `onSave` or `onType`, default is `onType`. - `eslint.quiet` - ignore warnings, default is `false`. -- `eslint.runtime` - use this setting to set the path of the node runtime to run ESLint under. [Use `"node"`](https://github.com/microsoft/vscode-eslint/issues/1233#issuecomment-815521280) if you want to use your default system version of node. +- `eslint.runtime` - use this setting to set the path of the node runtime to run ESLint under. [Use `"node"`](https://github.com/microsoft/vscode-eslint/issues/1233#issuecomment-815521280) along with [`"application.shellEnvironmentResolutionTimeout": 30`](https://github.com/microsoft/vscode-eslint/issues/1754#issuecomment-3410201863) if you want to use your default system version of node. - _NOTE_ If you are using remote connections (e.g., WSL, Remote SSH, DevContainer, etc.) and don’t want to modify workspace-wide settings, you need to run the "Preferences: Open Remote Settings (JSON)" command via the Command Palette. Set the desired options there, and then reload the editor to ensure the linter server applies the changes. - `eslint.execArgv` - use this setting to pass additional arguments to the node runtime like `--max-old-space-size=4096` - _NOTE_ If you are using remote connections (e.g., WSL, Remote SSH, DevContainer, etc.) and don’t want to modify workspace-wide settings, you need to run the "Preferences: Open Remote Settings (JSON)" command via the Command Palette. Set the desired options there, and then reload the editor to ensure the linter server applies the changes. @@ -489,3 +489,4 @@ As with JavaScript validating TypeScript in a mono repository requires that you Migrating from ESLint 5.x to ESLint 6.x might need some adaption (see the [ESLint Migration Guide](https://eslint.org/docs/user-guide/migrating-to-6.0.0) for details). Before filing an issue against the VS Code ESLint extension please ensure that you can successfully validate your files in a terminal using the eslint command. + From 3c335b9ac1e0bfa8273fab59c48d28633243e03a Mon Sep 17 00:00:00 2001 From: Karl Horky Date: Mon, 20 Oct 2025 16:15:47 +0200 Subject: [PATCH 2/3] Move shellEnvironmentResolutionTimeout to NOTE bullet --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 3d2cf397..ef80c859 100644 --- a/README.md +++ b/README.md @@ -322,7 +322,8 @@ This extension contributes the following variables to the [settings](https://cod - `eslint.useESLintClass` (@since 2.2.0) - whether to use the ESLint class API even if the CLIEngine API is present. The setting is only honor when using ESLint version 7.x. - `eslint.run` - run the linter `onSave` or `onType`, default is `onType`. - `eslint.quiet` - ignore warnings, default is `false`. -- `eslint.runtime` - use this setting to set the path of the node runtime to run ESLint under. [Use `"node"`](https://github.com/microsoft/vscode-eslint/issues/1233#issuecomment-815521280) along with [`"application.shellEnvironmentResolutionTimeout": 30`](https://github.com/microsoft/vscode-eslint/issues/1754#issuecomment-3410201863) if you want to use your default system version of node. +- `eslint.runtime` - use this setting to set the path of the node runtime to run ESLint under. [Use `"node"`](https://github.com/microsoft/vscode-eslint/issues/1233#issuecomment-815521280) if you want to use your default system version of node. + - _NOTE_ If the error `Unable to resolve your shell environment in a reasonable time.` appears, consider increasing timeout in [`application.shellEnvironmentResolutionTimeout`](https://code.visualstudio.com/updates/v1_75#_setting-to-configure-shell-environment-resolution-timeout) - _NOTE_ If you are using remote connections (e.g., WSL, Remote SSH, DevContainer, etc.) and don’t want to modify workspace-wide settings, you need to run the "Preferences: Open Remote Settings (JSON)" command via the Command Palette. Set the desired options there, and then reload the editor to ensure the linter server applies the changes. - `eslint.execArgv` - use this setting to pass additional arguments to the node runtime like `--max-old-space-size=4096` - _NOTE_ If you are using remote connections (e.g., WSL, Remote SSH, DevContainer, etc.) and don’t want to modify workspace-wide settings, you need to run the "Preferences: Open Remote Settings (JSON)" command via the Command Palette. Set the desired options there, and then reload the editor to ensure the linter server applies the changes. From 2f9d4f749074e99bb27d873bc23a83d960bd4a5f Mon Sep 17 00:00:00 2001 From: Karl Horky Date: Mon, 20 Oct 2025 16:16:15 +0200 Subject: [PATCH 3/3] Remove newline at end of file --- README.md | 1 - 1 file changed, 1 deletion(-) diff --git a/README.md b/README.md index ef80c859..6072f26b 100644 --- a/README.md +++ b/README.md @@ -490,4 +490,3 @@ As with JavaScript validating TypeScript in a mono repository requires that you Migrating from ESLint 5.x to ESLint 6.x might need some adaption (see the [ESLint Migration Guide](https://eslint.org/docs/user-guide/migrating-to-6.0.0) for details). Before filing an issue against the VS Code ESLint extension please ensure that you can successfully validate your files in a terminal using the eslint command. -