vscode-eslint 0.0.2 → 0.0.4

package/CHANGELOG.md

@@ -1,524 +0,0 @@
-### Version 3.0.24 - release
-
-- [Bug fixes](https://github.com/microsoft/vscode-eslint/issues?q=is%3Aissue%20state%3Aclosed%20milestone%3A3.20.0)
-
-### Version 3.0.22 - release
-
-- Release number skipped
-
-### Version 3.0.21 - pre-release
-
-- move to latest LSP libraries
-- `eslint.quite` blocks info messages as well.
-
-### Version 3.0.20 - release
-
-- [Bug fixes](https://github.com/microsoft/vscode-eslint/issues?q=is%3Aissue%20state%3Aclosed%20milestone%3A3.20.0)
-
-- [PRs](https://github.com/microsoft/vscode-eslint/pulls?q=is%3Apr+milestone%3A3.20.0+is%3Aclosed)
-
-### Version 3.0.19 - pre-release
-
-- move to latest LSP libraries
-
-### Version 3.0.17 - pre-release
-
-- add probe support for css
-
-### Version 3.0.16 - release
-
-- [Bug fixes](https://github.com/microsoft/vscode-eslint/issues?q=is%3Aissue%20state%3Aclosed%20milestone%3A3.16.0)
-
-- same as 3.15.0 - pre-release
-
-### Version 3.0.15 - pre-release
-
-- move to latest LSP libraries
-
-### Version 3.0.13 - pre-release
-
-- move to latest LSP libraries
-
-### Version 3.0.11 - pre-release
-
-- Enforcement of the validate setting. If the `eslint.validate` setting is specified only files in that list will be validated. For example, a setting of the form
-  ```
-  "eslint.validate": [
- 	  "javascript"
-  ]
-  ```
-  will only validate JavaScript files. This is comparable to providing extensions on the command line.
-
-### Version 3.0.10 - Release
-
-- Bump VS Code version to 1.90 to ensure NodeJS 20.
-
-### Version 3.0.8 - Release
-
-- Same as 3.0.7 - pre-release
-
-### Version 3.0.7 - pre-release
-
-- bug fixes to better support flat configs.
-
-### Version 3.0.5 - pre-release
-
-- Support for the new ESLint flat config files has improved. See README.MD for a detailed description of the changes.
-
-### Version 3.0.1 - pre-release
-
-- converted the server to use diagnostic pull instead of push.
-- files will be revalidated on focus gain.
-- Add a command `ESLint: Revalidate all open files` to revalidate all open files.
-- Probing support for [Astro](https://github.com/microsoft/vscode-eslint/pull/1795), [MDX](https://github.com/microsoft/vscode-eslint/pull/1794) and [JSON](https://github.com/microsoft/vscode-eslint/pull/1787)
-- various [bug fixes](https://github.com/microsoft/vscode-eslint/issues?q=is%3Aclosed+milestone%3ANext)
-
-### Version 2.4.4
-
-- same as 2.4.3 - pre-release
-
-### Version 2.4.3 - pre-release
-
-- various [bug fixes](https://github.com/microsoft/vscode-eslint/milestone/74?closed=1)
-
-### Version 2.4.2
-
-- same as 2.4.1 pre-release.
-
-### Version 2.4.1 - Pre-release
-
-- various [bug fixes](https://github.com/microsoft/vscode-eslint/milestone/51?closed=1)
-
-### Version 2.4.0 (same as 2.3.5 - Pre-release)
-
-- added settings options to control the time budget for validation and fix on save before a
-  warning or error is raised. The settings are `eslint.timeBudget.onValidation` and `eslint.timeBudget.onFixes`
-- make server `untitled` agnostic
-- the extension uses now VS Code's language status indicator
-- the language status indicator now informs about long linting or fix on save times.
-- the setting `eslint.alwaysShowStatus` got removed since the status is now shown as a language status indicator.
-- support for flat config files
-- support for single problem underline.
-- various [bug fixes](https://github.com/microsoft/vscode-eslint/issues?q=is%3Aclosed+milestone%3A2.4.0)
-
-### Version 2.3.5 - Pre-release
-
-- added settings options to control the time budget for validation and fix on save before a
-  warning or error is raised. The settings are `eslint.timeBudget.onValidation` and `eslint.timeBudget.onFixes`
-
-### Version 2.3.3 - Pre-release
-
-- make server `untitled` agnostic
-
-### Version 2.3.1 - Pre-release (internal only)
-
-- the extension uses now VS Code's language status indicator
-- the language status indicator now informs about long linting or fix on save times.
-- the setting `eslint.alwaysShowStatus` got removed since the status is now shown as a language status indicator.
-
-### Version 2.2.6
-
-- added support for validating single notebook document cells if the language is supported by ESLint
-- various [bug fixes](https://github.com/microsoft/vscode-eslint/milestone/47?closed=1)
-
-### 2.2.2
-
-- renamed the setting `eslint.runtime.execArgv` to `eslint.execArgv`. This is breaking but can't be fixed different due to how VS Code handles settings. See also [Issue 1358](https://github.com/microsoft/vscode-eslint/issues/1358)
-
-### 2.2.1
-
-Extended support for ESLint V8.0. This release also provides an option to use the new ESLint class API introduced in version 7 of the ESLint npm module. The corresponding setting is `eslint.useESLintClass`. In addition the rules taken into consideration during code action on save can now be configured. However this feature requires the new ESLint class API. So you either need to use ESLint version 8 or version 7 with `"eslint.useESLintClass": true`.
-
-### 2.2.0
-
-- Internal insider release.
-
-### 2.1.25
-
-- Added support for ESLint v8 Beta
-- Various [bug fixes](https://github.com/microsoft/vscode-eslint/issues?q=is%3Aclosed+milestone%3A2.1.25)
-
-### 2.1.24
-
-- Internal insider release.
-
-### 2.1.23
-
-- Fixes [Server should provide default result for code actions so that canceled requests can be removed from queue](https://github.com/microsoft/vscode-eslint/issues/1283)
-
-### 2.1.22
-
-- adapt VS Code's workspace trust model. As a consequence the custom dialog ESLint introduced in version `2.1.7` got removed.
-- Various [bug fixes](https://github.com/microsoft/vscode-eslint/issues?q=milestone%3A2.1.22+)
-
-
-### 2.1.21
-
-- Internal insider release.
-
-### 2.1.20
-
-- Merged [Implement eslint.rules.customizations - with overrides](https://github.com/microsoft/vscode-eslint/pull/1164)
-
-### 2.1.19
-
-- fixed [Using `eslint.nodePath` globally rather than locally, yet on every new window: `The eslint.nodePath setting requires user confirmation. To do so execute the Select Node Path command.`](https://github.com/microsoft/vscode-eslint/issues/1203)
-
-### 2.1.18
-
-- warn about nodePath values being defined separately in the workspace folder although a multi workspace folder setup is open.
-
-### 2.1.17
-
-- add user confirmation for the `eslint.runtime` and the `eslint.nodePath` setting
-- fixed [command to restart server or plugins without quitting vscode](https://github.com/microsoft/vscode-eslint/issues/164)
-
-### 2.1.16
-
-- Updated Readme document.
-
-### 2.1.15
-
-- Internal insider release.
-
-### 2.1.14
-
-- Update to version 7.0.0 of the LSP libraries
-- Various [bug fixes](https://github.com/microsoft/vscode-eslint/issues?q=is%3Aissue+is%3Aclosed+milestone%3A2.1.14).
-
-### 2.1.13
-
-- [v2.1.10 - Extension 'ESlint' cannot format file](https://github.com/microsoft/vscode-eslint/issues/1086)
-
-### 2.1.11 & 2.1.12
-
-- Internal insider release.
-
-### 2.1.10
-
-- Add an 'Always Allow' to the library confirmation dialog added in 2.1.7. Also added a status indication show the ESLint library decision mode.
-- Fixed vulnerability described in [CVE-2021-27081](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2021-27081)
-
-### 2.1.9
-
-- Internal insider release.
-
-### 2.1.8
-
-- Polish the message of the confirmation dialog that was introduced in 2.1.7
-- Fix bug that caused the confirmation dialog to pop up for all open editors when not trusting the local version of VS Code
-
-### 2.1.7
-
-- Ask the user for confirmation before executing the code from an installed ESLint library. Also added commands to manage the decisions made for the ESLint libraries.
-
-### 2.1.6
-
-- Update LSP libraries
-
-### 2.1.5
-
-- [UnhandledPromiseRejectionWarning: Error: Request workspace/configuration failed with message: Cannot read property 'source.fixAll.eslint' of null](https://github.com/microsoft/vscode-eslint/issues/950)
-- ["Do you want Code to open the external website?" on ESLint errors](https://github.com/microsoft/vscode-eslint/issues/949)
-- [all suggestions being applied on save](https://github.com/microsoft/vscode-eslint/issues/947)
-- [Error: "Cannot read property 'source.fixAll.eslint' of null"](https://github.com/microsoft/vscode-eslint/issues/945)
-
-### 2.1.4
-
-- Was used as an insider preview release.
-
-### 2.1.3
-
-- [FixAll on save doesn't pick up file change from organize imports](https://github.com/microsoft/vscode-eslint/issues/939)
-
-### 2.1.2
-
-- [Adopt new link support in diagnostics](https://github.com/microsoft/vscode-eslint/issues/911)
-
-### 2.1.1
-
-- [Support for ESLint suggest API](https://github.com/microsoft/vscode-eslint/pull/814)
-
-### 2.0.15
-
-- Update to latest LSP libraries
-
-### 2.0.14
-
-- [Auto fix made double comma to fix trailing comma](https://github.com/microsoft/vscode-eslint/issues/871)
-
-### 2.0.13
-
-- Fixes [no validation of .vue files (2.0.12)](https://github.com/microsoft/vscode-eslint/issues/870)
-
-### 2.0.12
-
-- Improved performance for code actions on save by reusing fixes for already known problems.
-- Added a setting `eslint.codeActionsOnSave.mode` to revive the 1.9.x version behavior of only fixing already known problems on save.
-- Bug fixes:
-  - [Can't lint .ts files when use vue-eslint-parser](https://github.com/microsoft/vscode-eslint/issues/864)
-
-### 2.0.11
-
-- Fixes [Eslint not working when open above level directory](https://github.com/microsoft/vscode-eslint/issues/854)
-
-### 2.0.10
-
-- Various bug fixes especially around settings migration.
-
-### 2.0.4
-
-A new major version of the extension. Major improvements are around code actions on save, formatting, working directory setup and validating of TypeScript files.
-
-### 1.9.2
-
-- Moved to latest LSP libraries
-- Fixed [Document change might not cause re-validation. Results in stale errors](https://github.com/microsoft/vscode-eslint/issues/758)
-- Merged [Fix None position values in publishDiagnostics message](https://github.com/microsoft/vscode-eslint/pull/753)
-
-### 1.9.1
-
-- Moved to latest LSP libraries
-- Add experimental support for delta document sync
-- Add support for [eslint.lintTask.options] (https://github.com/microsoft/vscode-eslint/pull/698)
-- Add support for `eslint.experimental.incrementalSync` which enable incremental document synchronization for improved performance.
-
-### 1.9.0
-
-- Moved to latest LSP libraries
-- Added support for [eslint.quiet](https://github.com/microsoft/vscode-eslint/pull/661)
-
-### 1.8.2
-
-- Fix version mismatch problem between LSP client lib and VS Code version.
-
-### 1.8.1
-
-- Moved to latest LSP libraries
-- Web pack extension and server
-- Fixes [Extension causes high CPU load](https://github.com/Microsoft/vscode-eslint/issues/620)
-
-### 1.8.0
-
-- Moved to latest LSP libraries
-- Merged in [PR #588](https://github.com/Microsoft/vscode-eslint/pull/588/) which adds to turn off the actions to disable rules per line and to open the documentation.
-- Merged in [PR #572](https://github.com/Microsoft/vscode-eslint/pull/572) which adds support for pnpm.
-
-### 1.7.0
-
-- Merged in [PR #530](https://github.com/Microsoft/vscode-eslint/pull/530) which adds support to disable a rule per line or for the whole file as well as navigating to the documentation.
-
-### 1.6.1
-
-- Fixes [#558](https://github.com/Microsoft/vscode-eslint/issues/558) to adopt new functionality in VS Code 1.28
-
-### 1.6.0
-
-- Adopt the LSP JSON tracing options from the LSP libraries to enable better tracing support
-
-### 1.5.0
-
-- Allow setting the node runtime to use for the language server. Fixes #345 [PR #516](https://github.com/Microsoft/vscode-eslint/pull/516)
-- eslintignore comment syntax highlighting [PR #473](https://github.com/Microsoft/vscode-eslint/pull/473)
-
-### 1.4.14
-
-- Include `semver` for client
-
-### 1.4.13
-
-- Upgraded to latest LSP libraries to handle process spawn / fork crashes under Electron 2.x
-
-### 1.4.12
-
-- Upgrade to latest version of the LSP libraries
-- Fixes [ESLint server crashed 5 times in the last 3 minutes. the server will not be restarted.](https://github.com/Microsoft/vscode-eslint/issues/437)
-
-### 1.4.11
-
-Internal version to track down [ESLint server crashed 5 times in the last 3 minutes. the server will not be restarted.](https://github.com/Microsoft/vscode-eslint/issues/437)
-
-### 1.4.10
-
-- [Add Command to create a YAML configuration](https://github.com/Microsoft/vscode-eslint/issues/409)
-
-### 1.4.9
-
-- Using latest vscode-languageclient library to fix problems with server restarts and double change notifications.
-
-### 1.4.8
-
-- Using latest vscode-languageclient library to get rid of unnecessary console.log statements.
-
-### 1.4.7
-
-- [extension not working](https://github.com/Microsoft/vscode-eslint/issues/365)
-- [Create a task provider for linting the whole workspace](https://github.com/Microsoft/vscode-eslint/pull/410)
-
-### 1.4.6
-
-- [Rename server.js to a more specific name so that ESLint is easily recognized by code --status](https://github.com/Microsoft/vscode-eslint/issues/406)
-
-### 1.4.5
-
-- [UnhandledPromiseRejectionWarning when renaming .eslintrc.json](https://github.com/Microsoft/vscode-eslint/issues/403)
-- [update error message and add a hint to update yarn setting if using yarn](https://github.com/Microsoft/vscode-eslint/pull/390)
-
-### 1.4.4
-
-- [request: better error message if ESLint crashes](https://github.com/Microsoft/vscode-eslint/issues/391)
-
-### 1.4.3
-
-- Moved to version 3.5.0 of the vscode-languageserver-node libraries.
-
-### 1.4.2
-
-- [ESLint should show a warning icon when something failed in the status bar](https://github.com/Microsoft/vscode-eslint/issues/328)
-
-### 1.4.1
-
-- small setting description fix.
-- tagged extension as multi root ready.
-
-### 1.4.0
-
-- Add support for [Yarn](https://yarnpkg.com/lang/en/). To use yarn instead of npm with the ESLint extension set the settings `"eslint.packageManager": "yarn"`. To use npm set the value to `"npm"`.
-
-### 1.3.2
-
-- [Latest update appears to have broken nodePath specification ](https://github.com/Microsoft/vscode-eslint/issues/298)
-
-### 1.3.1
-
-- [Failed to lint Untitled JavaScript file.](https://github.com/Microsoft/vscode-eslint/issues/295)
-
-### 1.3.0
-
-- Add support for multi workspace folder setups. Adding this support required a major code change both on the extension and the server side. So if you recognized problems with this version please report them as quick as possible in the [GitHub repository](https://github.com/Microsoft/vscode-eslint).
-
-  Version 1.3.0 of the ESLint extension requires at least version 1.16 of VS Code.
-
-### 1.2.11
-
-- [(Insiders/1.2.10) "Cannot read property 'then' of undefined](https://github.com/Microsoft/vscode-eslint/issues/240)
-
-### 1.2.10
-
-Performance work around code actions and validation. Fixed:
-
-- [Slowdown on code assist with ESLint enabled](https://github.com/Microsoft/vscode-eslint/issues/215)
-
-### 1.2.9
-
-This version was an internal test release which wasn't available in the market place
-
-### 1.2.8
-
-- [Linting is still enabled when viewing git diff.](https://github.com/Microsoft/vscode-eslint/issues/216)
-
-### 1.2.7
-
-- [Don't lint git diff.](https://github.com/Microsoft/vscode-eslint/issues/200)
-
-### 1.2.6
-
-- [Do not always run ESLint from the project's root directory](https://github.com/Microsoft/vscode-eslint/issues/196)
-- [baseDir should be an absolute path](https://github.com/Microsoft/vscode-eslint/issues/202)
-
-
-### <a name="RN125"></a>1.2.5
-
-- Validating a single file (no workspace folder open) will set the working directory to the directory containing the file.
-- Added support for working directories. ESLint resolves configuration files relative to a working directory. This new settings allows users to control which working directory is used for which files. Consider the following setups:
-
-```
-client/
-  .eslintignore
-  .eslintrc.json
-  client.js
-server/
-  .eslintignore
-  .eslintrc.json
-  server.js
-```
-
-Then using the setting:
-```json
-  "eslint.workingDirectories": [
-    "./client", "./server"
-  ]
-```
-will validate files inside the server directory with the server directory as the current working directory. Same for files in the client directory. If the setting is omitted the working directory is the workspace folder.
-
-
-### 1.2.4
-
-- fixes [.eslintignore is completely ignored](https://github.com/Microsoft/vscode-eslint/issues/198)
-- reverted fix for [Does not respect nested eslintignore files](https://github.com/Microsoft/vscode-eslint/issues/111) since it broke the use case of a single global .eslintrc file
-
-### 1.2.3
-
-- [Does not respect nested eslintignore files](https://github.com/Microsoft/vscode-eslint/issues/111)
-- [eslintrc configuration cascading not being honored ](https://github.com/Microsoft/vscode-eslint/issues/97)
-- [autoFixOnSave not working with eslint.run=onSave](https://github.com/Microsoft/vscode-eslint/issues/158)
-- [autoFixOnSave not listed under Settings Options in Readme](https://github.com/Microsoft/vscode-eslint/issues/188)
-
-### 1.2.2
-
-- Added configuration options to enable code actions and auto fix on save selectively per language. In release 1.2.1 code actions and auto fix on save very still only
-available for JavaScript. In 1.2.2 you can now enable this selectively per language. For compatibility it is enabled by default for JavaScript and disabled by default for all
-other languages. The reason is that I encounter cases for non JavaScript file types where the computed fixes had wrong positions resulting in 'broken' documents. To enable it simply
-provide an object literal in the validate setting with the properties `language` and `autoFix` instead of a simple `string`. An example is:
-```json
-"eslint.validate": [ "javascript", "javascriptreact", { "language": "html", "autoFix": true } ]
-```
-
-### <a name="RN121"></a>1.2.1
-
-- Added support to validate file types other than JavaScript. To enable this, you need to do the following:
-  - Configure ESLint with an additional plugin to do the actual validation. For example, to validate HTML files install
-`eslint-plugin-html` using `npm install eslint-plugin-html --save-dev` and update the ESLint configuration (e.g. .eslintrc.json file)
-with `"plugin": [ "html" ]`.
-  - Add the corresponding language identifier to the `eslint.validate` setting. Something like `"eslint.validate": [ "javascript", "javascriptreact", "html" ]`.
-If the setting is missing, it defaults to `["javascript", "javascriptreact"]`
-
-Please note that code actions and auto fix on save is still only available for JavaScript. The reason is that I detected position problems with fixes contributed by plugins
-resulting in broken source code when applied.
-
-### 1.1.0
-
-- Supports more than one ESLint module installation in a workspace. This eases working with typical client / server setups where ESLint is installed
-in a `node_modules` folder in the `server` and the `client` directory.
-- Improved error handling if a plugin can't be loaded.
-- Added commands to enable and disable ESLint.
-
-### 1.0.8
-
-- Supports auto fix on save. Needs to be enabled via `"eslint.autoFixOnSave": true`. Please note that auto fix on save will only happen
-if the save happened manually or via focus lost. This is consistent with VS Code's format on save behavior. Auto fix on save requires
-VS Code version 1.6 or newer.
-
-### 1.0.7
-
-- Fixed problem with validating package.json when editing .eslintrc.* files.
-
-### 1.0.5
-
-- Moving to official 2.5.0 language server libraries.
-
-### 1.0.4
-
-- Bug fixing: ESLint is validating package.json files
-
-### 1.0.3
-
-- Errors in configuration files are only shown in a status message if the file is not open in the editor. Otherwise message are shown in the output channel only.
-
-### 1.0.2
-
-- Added a status bar item to inform the user about problems with ESLint. A message box only appears if the user attention is required.
-- Improved handling of missing corrupted configuration files.
-- The ESLint package is now loaded from parent folders as well.
-- Added an action to create a .eslintrc.json file.
-

package/SECURITY.md

@@ -1,41 +0,0 @@
-<!-- BEGIN MICROSOFT SECURITY.MD V0.0.5 BLOCK -->
-
-## Security
-
-Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include [Microsoft](https://github.com/Microsoft), [Azure](https://github.com/Azure), [DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet), [Xamarin](https://github.com/xamarin), and [our GitHub organizations](https://opensource.microsoft.com/).
-
-If you believe you have found a security vulnerability in any Microsoft-owned repository that meets [Microsoft's definition of a security vulnerability](https://docs.microsoft.com/en-us/previous-versions/tn-archive/cc751383(v=technet.10)), please report it to us as described below.
-
-## Reporting Security Issues
-
-**Please do not report security vulnerabilities through public GitHub issues.**
-
-Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://msrc.microsoft.com/create-report).
-
-If you prefer to submit without logging in, send email to [secure@microsoft.com](mailto:secure@microsoft.com).  If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://www.microsoft.com/en-us/msrc/pgp-key-msrc).
-
-You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at [microsoft.com/msrc](https://www.microsoft.com/msrc).
-
-Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
-
-  * Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
-  * Full paths of source file(s) related to the manifestation of the issue
-  * The location of the affected source code (tag/branch/commit or direct URL)
-  * Any special configuration required to reproduce the issue
-  * Step-by-step instructions to reproduce the issue
-  * Proof-of-concept or exploit code (if possible)
-  * Impact of the issue, including how an attacker might exploit the issue
-
-This information will help us triage your report more quickly.
-
-If you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Please visit our [Microsoft Bug Bounty Program](https://microsoft.com/msrc/bounty) page for more details about our active programs.
-
-## Preferred Languages
-
-We prefer all communications to be in English.
-
-## Policy
-
-Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://www.microsoft.com/en-us/msrc/cvd).
-
-<!-- END MICROSOFT SECURITY.MD BLOCK -->

package/agents.md

@@ -1,36 +0,0 @@
-## High-Level Overview
-
-The extension integrates ESLint into VS Code by implementing a ESLint server using the [Language Server Protocol (LSP)](https://microsoft.github.io/language-server-protocol/).
-
-Key goals:
-* Defer activation until needed (lazy activation based on opened documents / settings).
-* Support multiple workspace folders & dynamic working directory inference.
-* Abstract ESLint version / API differences (CLIEngine vs ESLint class / flat config) transparently.
-* Provide rich code actions (fix all, rule disable, suggestions) and formatting integration.
-* Handle notebooks and non-file schemes where possible.
-
-
-## Repository Structure (Relevant Directories)
-
-| Path | Purpose |
-|------|---------|
-| `package.json` | Extension manifest, contributes settings/commands/tasks, build scripts. |
-| `client/` | Extension (frontend) code – activation, LSP client, task provider, status integration. |
-| `server/` | LSP server implementation – lint orchestration, diagnostics, code actions. |
-| `$shared/` | Shared protocol message & settings types. This folder is symlinked into `./client/src/shared` and `./server/src/shared`. |
-| `build/` | CI scripts, helper Node scripts (`bin/all.js`, install/link steps). |
-| `playgrounds/` | Sample projects used for manual testing across ESLint versions & config styles. |
-| `images/` | Assets for marketplace/readme. |
-
-## Settings
-
-Settings are retrieved using a scope where the scope can be global or per resource (folder or file). Therefore settings must never be stored in globals on the server side. The always need to be managed as `TextDocumentSettings` which are cached by the resource path.
-
-To add a new settings follow these steps:
-
-1. Add schema in root `package.json` under `contributes.configuration.properties`. New settings should default to a falsify value if not specified otherwise. All setting keys must be prefixed with `eslint`
-2. Extend `ConfigurationSettings` under `$shared/settings`.
-3. Map retrieval in `client/src/client.ts` `readConfiguration()`
-4. Use setting inside `eslint.ts` logic (e.g., adapt `validate()` or `resolveSettings()`).
-
-## Design Decisions

package/bin/vscode-eslint.js

@@ -1,56 +0,0 @@
-#!/usr/bin/env node
-
-/*---------------------------------------------------------------------------------------------
- *  Copyright (c) Microsoft Corporation. All rights reserved.
- *  Licensed under the MIT License. See License.txt in the project root for license information.
- *--------------------------------------------------------------------------------------------*/
-
-'use strict';
-
-const path = require('path');
-const { spawn } = require('child_process');
-
-function usage(exitCode = 0) {
-	const msg = [
-		'vscode-eslint (LSP server)',
-		'',
-		'Usage:',
-		'  vscode-eslint --stdio',
-		'',
-		'Options:',
-		'  --stdio     Use stdio transport (LSP over JSON-RPC on stdin/stdout)',
-		'  -h, --help  Show this help',
-	].join('\n');
-	if (exitCode === 0) {
-		process.stdout.write(msg + '\n');
-	} else {
-		process.stderr.write(msg + '\n');
-	}
-	process.exit(exitCode);
-}
-
-const args = process.argv.slice(2);
-if (args.includes('-h') || args.includes('--help')) {
-	usage(0);
-}
-
-const wantsStdio = args.includes('--stdio');
-if (!wantsStdio) {
-	process.stderr.write('error: missing required --stdio\n\n');
-	usage(2);
-}
-
-// Run the bundled server produced by server/webpack.config.js
-const serverEntry = path.resolve(__dirname, '..', 'server', 'out', 'eslintServer.js');
-
-const child = spawn(process.execPath, [serverEntry], {
-	stdio: 'inherit'
-});
-
-child.on('exit', (code, signal) => {
-	if (signal) {
-		process.exitCode = 1;
-		return;
-	}
-	process.exitCode = code ?? 0;
-});

package/build/azure-pipelines/linux/build.yml

@@ -1,14 +0,0 @@
-steps:
-- task: NodeTool@0
-  inputs:
-    versionSpec: '20.14.0'
-  displayName: 'Use Node.js 20.14.0'
-
-- script: |
-    npm ci
-  displayName: 'Install dependencies'
-
-- script: |
-    npm run lint
-    npm run compile
-  displayName: 'Lint & Compile'