tomit4/notes
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

added vscode extensions

Browse source
This commit is contained in:
tomit4 2021-11-05 11:26:45 -07:00
parent 7cde0829be
commit 26e2a50441
316 changed files with 37301 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

44
.vscode/extensions/dbaeumer.vscode-eslint-2.1.23/.vsixmanifest vendored Normal file
View file

@ -0,0 +1,44 @@
<?xml version="1.0" encoding="utf-8"?>
<PackageManifest Version="2.0.0" xmlns="http://schemas.microsoft.com/developer/vsx-schema/2011" xmlns:d="http://schemas.microsoft.com/developer/vsx-schema-design/2011">
<Metadata>
<Identity Language="en-US" Id="vscode-eslint" Version="2.1.23" Publisher="dbaeumer"/>
<DisplayName>ESLint</DisplayName>
<Description xml:space="preserve">Integrates ESLint JavaScript into VS Code.</Description>
<Tags>multi-root ready,json,ignore,__ext_eslintignore,jsonc,javascript,linters</Tags>
<Categories>Programming Languages,Linters</Categories>
<GalleryFlags>Public</GalleryFlags>
<Badges></Badges>
<Properties>
<Property Id="Microsoft.VisualStudio.Code.Engine" Value="^1.57.0" />
<Property Id="Microsoft.VisualStudio.Code.ExtensionDependencies" Value="" />
<Property Id="Microsoft.VisualStudio.Code.ExtensionPack" Value="" />
<Property Id="Microsoft.VisualStudio.Code.ExtensionKind" Value="workspace" />
<Property Id="Microsoft.VisualStudio.Code.LocalizedLanguages" Value="" />
<Property Id="Microsoft.VisualStudio.Services.Links.Source" Value="https://github.com/Microsoft/vscode-eslint.git" />
<Property Id="Microsoft.VisualStudio.Services.Links.Getstarted" Value="https://github.com/Microsoft/vscode-eslint.git" />
<Property Id="Microsoft.VisualStudio.Services.Links.GitHub" Value="https://github.com/Microsoft/vscode-eslint.git" />
<Property Id="Microsoft.VisualStudio.Services.Links.Support" Value="https://github.com/Microsoft/vscode-eslint/issues" />
<Property Id="Microsoft.VisualStudio.Services.GitHubFlavoredMarkdown" Value="true" />
</Properties>
<License>extension/License.txt</License>
<Icon>extension/eslint_icon.png</Icon>
</Metadata>
<Installation>
<InstallationTarget Id="Microsoft.VisualStudio.Code"/>
</Installation>
<Dependencies/>
<Assets>
<Asset Type="Microsoft.VisualStudio.Code.Manifest" Path="extension/package.json" Addressable="true" />
<Asset Type="Microsoft.VisualStudio.Services.Content.Details" Path="extension/README.md" Addressable="true" /><Asset Type="Microsoft.VisualStudio.Services.Content.Changelog" Path="extension/CHANGELOG.md" Addressable="true" /><Asset Type="Microsoft.VisualStudio.Services.Content.License" Path="extension/License.txt" Addressable="true" /><Asset Type="Microsoft.VisualStudio.Services.Icons.Default" Path="extension/eslint_icon.png" Addressable="true" />
</Assets>
</PackageManifest>

393
.vscode/extensions/dbaeumer.vscode-eslint-2.1.23/CHANGELOG.md vendored Normal file
View file

@ -0,0 +1,393 @@
### 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
- Bug Fixes:
- [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/issues/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/issues/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/issues/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](https://github.com/Microsoft/vscode-eslint/issues/345) [PR [#516](https://github.com/Microsoft/vscode-eslint/issues/516)](https://github.com/Microsoft/vscode-eslint/pull/516)
- eslintignore comment syntax highlighting [PR [#473](https://github.com/Microsoft/vscode-eslint/issues/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
Fixes:
- [Latest update appears to have broken nodePath specification ](https://github.com/Microsoft/vscode-eslint/issues/298)
### 1.3.1
Fixes:
- [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
Fixes:
- [(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
### Fixes:
- [Linting is still enabled when viewing git diff.](https://github.com/Microsoft/vscode-eslint/issues/216)
### 1.2.7
#### Fixes:
- [Don't lint git diff.](https://github.com/Microsoft/vscode-eslint/issues/200)
### 1.2.6
#### Fixes:
- [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
- Bug fixes:
- [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.

17
.vscode/extensions/dbaeumer.vscode-eslint-2.1.23/License.txt vendored Normal file
View file

@ -0,0 +1,17 @@
Copyright (c) Microsoft Corporation
All rights reserved.
MIT License
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files
(the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge,
publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do
so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED *AS IS*, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE
FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

261
.vscode/extensions/dbaeumer.vscode-eslint-2.1.23/README.md vendored Normal file
View file

@ -0,0 +1,261 @@
# VS Code ESLint extension
[![Build Status](https://dev.azure.com/ms/vscode-eslint/_apis/build/status/Microsoft.vscode-eslint)](https://dev.azure.com/ms/vscode-eslint/_build/latest?definitionId=18)
Integrates [ESLint](http://eslint.org/) into VS Code. If you are new to ESLint check the [documentation](http://eslint.org/).
The extension uses the ESLint library installed in the opened workspace folder. If the folder doesn't provide one the extension looks for a global install version. If you haven't installed ESLint either locally or globally do so by running `npm install eslint` in the workspace folder for a local install or `npm install -g eslint` for a global install.
On new folders you might also need to create a `.eslintrc` configuration file. You can do this by either using the VS Code command `Create ESLint configuration` or by running the `eslint` command in a terminal. If you have installed ESLint globally (see above) then run [`eslint --init`](http://eslint.org/docs/user-guide/command-line-interface) in a terminal. If you have installed ESLint locally then run [`.\node_modules\.bin\eslint --init`](http://eslint.org/docs/user-guide/command-line-interface) under Windows and [`./node_modules/.bin/eslint --init`](http://eslint.org/docs/user-guide/command-line-interface) under Linux and Mac.
## Release Notes
This section describes major releases and their improvements. For a detailed list of changes please refer to the [change log](https://github.com/Microsoft/vscode-eslint/blob/HEAD/./CHANGELOG.md);
### Version 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. In addition the `off` value got added to the eslint rule customization support.
### Version 2.1.20
Added support to customize the severity of eslint rules. See the new setting `eslint.rules.customizations`.
### Version 2.1.18
Asking for confirmation of the `eslint.nodePath` value revealed a setup where that value is defined separately on a workspace folder level although a multi workspace folder setup is open (e.g. a code-workspace file). These setups need to define the `eslint.nodePath` value in the corresponding `code-workspace` file and the extension now warns the user about it. Below an example of such a `code-workspace` file
```json
{
"folders": [
{
"path": "project-a"
},
{
"path": "project-b"
}
],
"settings": {
"eslint.nodePath": "myCustomNodePath"
}
}
```
### Version 2.1.17
To follow VS Code's model to confirm workspace local settings that impact code execution the two settings `eslint.runtime` and `eslint.nodePath` now need user confirmation if defined locally in a workspace folder or a workspace file. Users using these settings in those local scopes will see a notification reminding them of the confirmation need.
The version also adds a command to restart the ESLint server.
### Version 2.1.10
The approval flow to allow the execution of a ESLint library got reworked. Its initial experience is now as follows:
- no modal dialog is shown when the ESLint extension tries to load an ESLint library for the first time and an approval is necessary. Instead the ESLint status bar item changes to ![ESLint status icon](https://github.com/Microsoft/vscode-eslint/raw/HEAD/images/2_1_10/eslint-status.png) indicating that the execution is currently block.
- if the active text editor content would be validated using ESLint, a problem at the top of the file is shown in addition.
The execution of the ESLint library can be denied or approved using the following gestures:
- clicking on the status bar icon
- using the quick fix for the corresponding ESLint problem
- executing the command `ESLint: Manage Library Execution` from the command palette
All gestures will open the following dialog:
![ESLint Dialog](https://github.com/Microsoft/vscode-eslint/raw/HEAD/images/2_1_10/eslint-dialog.png)
The chosen action is then reflected in the ESLint status bar item in the following way:
- `Allow` will prefix the status bar item with a check mark.
- `Allow Everywhere` will prefix the status bar item with a double check mark.
- `Deny` and `Disable` will prefix the status bar item with a blocked sign.
You can manage our decisions using the following commands:
- `ESLint: Manage Library Execution` will reopen aboves dialog
- `ESLint: Reset Library Decisions` lets you reset previous decisions who have made.
This release also addresses the vulnerability described in [CVE-2021-27081](https://msrc.microsoft.com/update-guide/vulnerability/CVE-2021-27081).
### Version 2.0.4
The 2.0.4 version of the extension contains the following major improvements:
* Improved TypeScript detection - As soon as TypeScript is correctly configured inside ESLint, you no longer need additional configuration through VS Code's `eslint.validate` setting. The same is true for HTML and Vue.js files.
* Glob working directory support - Projects that have a complex folder structure and need to customize the working directories via `eslint.workingDirectories` can now use glob patterns instead of listing every project folder. For example, `{ "pattern": "code-*" }` will match all project folders starting with `code-`. In addition, the extension now changes the working directory by default. You can disable this feature with the new `!cwd` property.
* Formatter support: ESLint can now be used as a formatter. To enable this feature use the `eslint.format.enable` setting.
* Improved Auto Fix on Save - Auto Fix on Save is now part of VS Code's Code Action on Save infrastructure and computes all possible fixes in one round. It is customized via the `editor.codeActionsOnSave` setting. The setting supports the ESLint specific property `source.fixAll.eslint`. The extension also respects the generic property `source.fixAll`.
The setting below turns on Auto Fix for all providers including ESLint:
```json
"editor.codeActionsOnSave": {
"source.fixAll": true
}
```
In contrast, this configuration only turns it on for ESLint:
```json
"editor.codeActionsOnSave": {
"source.fixAll.eslint": true
}
```
You can also selectively disable ESLint via:
```json
"editor.codeActionsOnSave": {
"source.fixAll": true,
"source.fixAll.eslint": false
}
```
Also note that there is a time budget of 750ms to run code actions on save which might not be enough for large JavaScript / TypeScript file. You can increase the time budget using the `editor.codeActionsOnSaveTimeout` setting.
The old `eslint.autoFixOnSave` setting is now deprecated and can safely be removed.
## Settings Options
If you are using an ESLint extension version < 2.x then please refer to the settings options [here](https://github.com/microsoft/vscode-eslint/blob/master/history/settings_1_9_x.md).
This extension contributes the following variables to the [settings](https://code.visualstudio.com/docs/customization/userandworkspace):
- `eslint.enable`: enable/disable ESLint. Is enabled by default. This setting got deprecated in favour of enabling / disabling the extension in the Extension's viewlet.
- `eslint.debug`: enables ESLint's debug mode (same as --debug command line option). Please see the ESLint output channel for the debug output. This options is very helpful to track down configuration and installation problems with ESLint since it provides verbose information about how ESLint is validating a file.
- `eslint.lintTask.enable`: whether the extension contributes a lint task to lint a whole workspace folder.
- `eslint.lintTask.options`: Command line options applied when running the task for linting the whole workspace (https://eslint.org/docs/user-guide/command-line-interface).
An example to point to a custom `.eslintrc.json` file and a custom `.eslintignore` is:
```json
{
"eslint.lintTask.options": "-c C:/mydirectory/.eslintrc.json --ignore-path C:/mydirectory/.eslintignore ."
}
```
- `eslint.packageManager`: controls the package manager to be used to resolve the ESLint library. This has only an influence if the ESLint library is resolved globally. Valid values are `"npm"` or `"yarn"` or `"pnpm"`.
- `eslint.options`: options to configure how ESLint is started using the [ESLint CLI Engine API](http://eslint.org/docs/developer-guide/nodejs-api#cliengine). Defaults to an empty option bag.
An example to point to a custom `.eslintrc.json` file is:
```json
{
"eslint.options": { "configFile": "C:/mydirectory/.eslintrc.json" }
}
```
- `eslint.run` - run the linter `onSave` or `onType`, default is `onType`.
- `eslint.quiet` - ignore warnings.
- `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.nodeEnv` - use this setting if an ESLint plugin or configuration needs `process.env.NODE_ENV` to be defined.
- `eslint.nodePath` - use this setting if an installed ESLint package can't be detected, for example `/myGlobalNodePackages/node_modules`.
- `eslint.probe` = an array for language identifiers for which the ESLint extension should be activated and should try to validate the file. If validation fails for probed languages the extension says silent. Defaults to `["javascript", "javascriptreact", "typescript", "typescriptreact", "html", "vue", "markdown"]`.
- `eslint.validate` - an array of language identifiers specifying the files for which validation is to be enforced. This is an old legacy setting and should in normal cases not be necessary anymore. Defaults to `["javascript", "javascriptreact"]`.
- `eslint.format.enable`: enables ESLint as a formatter for validated files. Although you can also use the formatter on save using the setting `editor.formatOnSave` it is recommended to use the `editor.codeActionsOnSave` feature since it allows for better configurability.
- `eslint.workingDirectories` - specifies how the working directories ESLint is using are computed. ESLint resolves configuration files (e.g. `eslintrc`, `.eslintignore`) relative to a working directory so it is important to configure this correctly. If executing ESLint in the terminal requires you to change the working directory in the terminal into a sub folder then it is usually necessary to tweak this setting. (see also [CLIEngine options#cwd](https://eslint.org/docs/developer-guide/nodejs-api#cliengine)). Please also keep in mind that the `.eslintrc*` file is resolved considering the parent directories whereas the `.eslintignore` file is only honored in the current working directory. The following values can be used:
- `[{ "mode": "location" }]` (@since 2.0.0): instructs ESLint to uses the workspace folder location or the file location (if no workspace folder is open) as the working directory. This is the default and is the same strategy as used in older versions of the ESLint extension (1.9.x versions).
- `[{ "mode": "auto" }]` (@since 2.0.0): instructs ESLint to infer a working directory based on the location of `package.json`, `.eslintignore` and `.eslintrc*` files. This might work in many cases but can lead to unexpected results as well.
- `string[]`: an array of working directories to use.
Consider the following directory layout:
```
root/
client/
.eslintrc.json
client.js
server/
.eslintignore
.eslintrc.json
server.js
```
Then using the setting:
```javascript
"eslint.workingDirectories": [ "./client", "./server" ]
```
will validate files inside the server directory with the server directory as the current eslint working directory. Same for files in the client directory. The ESLint extension will also change the process's working directory to the provided directories. If this is not wanted a literal with the `!cwd` property can be used (e.g. `{ "directory": "./client", "!cwd": true }`). This will use the client directory as the ESLint working directory but will not change the process`s working directory.
- `[{ "pattern": glob pattern }]` (@since 2.0.0): Allows to specify a pattern to detect the working directory. This is basically a short cut for listing every directory. If you have a mono repository with all your projects being below a packages folder you can use `{ "pattern": "./packages/*/" }` to make all these folders working directories.
- `eslint.codeAction.disableRuleComment` - object with properties:
- `enable` - show disable lint rule in the quick fix menu. `true` by default.
- `location` - choose to either add the `eslint-disable` comment on the `separateLine` or `sameLine`. `separateLine` is the default.
Example:
```json
{ "enable": true, "location": "sameLine" }
```
- `eslint.codeAction.showDocumentation` - object with properties:
- `enable` - show open lint rule documentation web page in the quick fix menu. `true` by default.
- `eslint.codeActionsOnSave.mode` (@since 2.0.12): controls which problems are fix when running code actions on save
- `all`: fixes all possible problems by revalidating the file's content. This executes the same code path as running eslint with the `--fix` option in the terminal and therefore can take some time. This is the default value.
- `problems`: fixes only the currently known fixable problems as long as their textual edits are non overlapping. This mode is a lot faster but very likely only fixes parts of the problems.
- `eslint.rules.customizations` (@since 2.1.20): force rules to report a different severity within VS Code compared to the project's true ESLint configuration. Contains two properties:
- `"rule`": Select on rules with names that match, factoring in asterisks as wildcards: `{ "rule": "no-*", "severity": "warn" }`
- Prefix the name with a `"!"` to target all rules that _don't_ match the name: `{ "rule": "!no-*", "severity": "info" }`
- `"severity"`: Sets a new severity for matched rule(s), `"downgrade"`s them to a lower severity, `"upgrade"`s them to a higher severity, or `"default"`s them to their original severity
In this example, all rules are overridden to warnings:
```json
"eslint.rules.customizations": [
{ "rule": "*", "severity": "warn" }
]
```
In this example, `no-` rules are informative, other rules are downgraded, and `"radix"` is reset to default:
```json
"eslint.rules.customizations": [
{ "rule": "no-*", "severity": "info" },
{ "rule": "!no-*", "severity": "downgrade" },
{ "rule": "radix", "severity": "default" }
]
```
- `eslint.format.enable` (@since 2.0.0): uses ESlint as a formatter for files that are validated by ESLint. If enabled please ensure to disable other formatters if you want to make this the default. A good way to do so is to add the following setting `"[javascript]": { "editor.defaultFormatter": "dbaeumer.vscode-eslint" }` for JavaScript. For TypeScript you need to add `"[typescript]": { "editor.defaultFormatter": "dbaeumer.vscode-eslint" }`.
- `eslint.onIgnoredFiles` (@since 2.0.10): used to control whether warnings should be generated when trying to lint ignored files. Default is `off`. Can be set to `warn`.
- `editor.codeActionsOnSave` (@since 2.0.0): this setting now supports an entry `source.fixAll.eslint`. If set to true all auto-fixable ESLint errors from all plugins will be fixed on save. You can also selectively enable and disabled specific languages using VS Code's language scoped settings. To disable `codeActionsOnSave` for HTML files use the following setting:
```json
"[html]": {
"editor.codeActionsOnSave": {
"source.fixAll.eslint": false
}
}
```
The old `eslint.autoFixOnSave` setting is now deprecated and can safely be removed. Please also note that if you use ESLint as your default formatter you should turn off `editor.formatOnSave` when you have turned on `editor.codeActionsOnSave`. Otherwise you file gets fixed twice which in unnecessary.
## Settings Migration
If the old `eslint.autoFixOnSave` option is set to true ESLint will prompt to convert it to the new `editor.codeActionsOnSave` format. If you want to avoid the migration you can respond in the dialog in the following ways:
- Not now: the setting will not be migrated by ESLint prompts again the next time you open the workspace
- Never migrate Settings: the settings migration will be disabled by changing the user setting `eslint.migration.2_x` to `off`
The migration can always be triggered manually using the command `ESLint: Migrate Settings`
## Commands:
This extension contributes the following commands to the Command palette.
- `Create '.eslintrc.json' file`: creates a new `.eslintrc.json` file.
- `Fix all auto-fixable problems`: applies ESLint auto-fix resolutions to all fixable problems.
- `Reset Library Decisions`: Resets the ESLint library validation confirmations.
- `Manage Library Execution`: Opens the library execution confirmation dialog.
## Using the extension with VS Code's task running
The extension is linting an individual file only on typing. If you want to lint the whole workspace set `eslint.lintTask.enable` to `true` and the extension will also contribute the `eslint: lint whole folder` task. There is no need anymore to define a custom task in `tasks.json`.
## Using ESLint to validate TypeScript files
A great introduction on how to lint TypeScript using ESlint can be found in the [TypeScript - ESLint](https://github.com/typescript-eslint/typescript-eslint). Please make yourself familiar with the introduction before using the VS Code ESLint extension in a TypeScript setup. Especially make sure that you can validate TypeScript files successfully in a terminal using the `eslint` command.
This project itself uses ESLint to validate its TypeScript files. So it can be used as a blueprint to get started.
To avoid validation from any TSLint installation disable TSLint using `"tslint.enable": false`.
### Mono repository setup
As with JavaScript validating TypeScript in a mono repository requires that you tell the VS Code ESLint extension what the current working directories are. Use the `eslint.workingDirectories` setting to do so. For this repository the working directory setup looks as follows:
```json
"eslint.workingDirectories": [ "./client", "./server" ]
```
## ESLint 6.x
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.

41
.vscode/extensions/dbaeumer.vscode-eslint-2.1.23/SECURITY.md vendored Normal file
View file

@ -0,0 +1,41 @@
<!-- 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 -->

31
.vscode/extensions/dbaeumer.vscode-eslint-2.1.23/ThirdPartyNotices.txt vendored Normal file
View file

@ -0,0 +1,31 @@
THIRD-PARTY SOFTWARE NOTICES AND INFORMATION
For Microsoft vscode-eslint
This project incorporates material from the project(s) listed below (collectively, “Third Party Code”).
Microsoft is not the original author of the Third Party Code. The original copyright notice and license
under which Microsoft received such Third Party Code are set out below. This Third Party Code is licensed
to you under their original license terms set forth below. Microsoft reserves all other rights not expressly
granted, whether by implication, estoppel or otherwise.
1. DefinitelyTyped version 0.0.1 (https://github.com/borisyankov/DefinitelyTyped)
This project is licensed under the MIT license.
Copyrights are respective of each contributor listed at the beginning of each definition file.
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.

2
.vscode/extensions/dbaeumer.vscode-eslint-2.1.23/client/out/extension.js vendored Normal file
View file

File diff suppressed because one or more lines are too long

28
.vscode/extensions/dbaeumer.vscode-eslint-2.1.23/client/package.json vendored Normal file
View file

@ -0,0 +1,28 @@
{
"name": "client",
"displayName": "ESLint",
"description": "Integrates ESLint into VS Code.",
"version": "2.1.20",
"private": true,
"author": "Microsoft Corporation",
"license": "MIT",
"repository": {
"type": "git",
"url": "https://github.com/Microsoft/vscode-eslint.git"
},
"bugs": {
"url": "https://github.com/Microsoft/vscode-eslint/issues"
},
"engines": {
"vscode": "^1.53.0"
},
"devDependencies": {
"@types/vscode": "1.53.0"
},
"dependencies": {
"vscode-languageclient": "7.0.0"
},
"scripts": {
"test": "node ../node_modules/mocha/bin/_mocha"
}
}

BIN
.vscode/extensions/dbaeumer.vscode-eslint-2.1.23/eslint_icon.png vendored Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 31 KiB

9
.vscode/extensions/dbaeumer.vscode-eslint-2.1.23/package-json-schema.json vendored Normal file
View file

@ -0,0 +1,9 @@
{
"$schema": "http://json-schema.org/draft-07/schema",
"properties": {
"eslintConfig": {
"description": "ESLint configuration",
"$ref": "http://json.schemastore.org/eslintrc"
}
}
}

513
.vscode/extensions/dbaeumer.vscode-eslint-2.1.23/package.json vendored Normal file
View file

@ -0,0 +1,513 @@
{
"name": "vscode-eslint",
"displayName": "ESLint",
"description": "Integrates ESLint JavaScript into VS Code.",
"version": "2.1.23",
"author": "Microsoft Corporation",
"license": "MIT",
"repository": {
"type": "git",
"url": "https://github.com/Microsoft/vscode-eslint.git"
},
"bugs": {
"url": "https://github.com/Microsoft/vscode-eslint/issues"
},
"publisher": "dbaeumer",
"icon": "eslint_icon.png",
"categories": [
"Programming Languages",
"Linters"
],
"keywords": [
"multi-root ready"
],
"engines": {
"vscode": "^1.57.0"
},
"activationEvents": [
"onStartupFinished"
],
"extensionKind": [
"workspace"
],
"main": "./client/out/extension",
"capabilities": {
"virtualWorkspaces": {
"supported": false,
"description": "Using ESLint is not possible in virtual workspaces."
},
"untrustedWorkspaces": {
"supported": false,
"description": "The extension requires workspace trust because it loads configuration files and code from the workspace and executes it."
}
},
"contributes": {
"configuration": {
"type": "object",
"title": "ESLint",
"properties": {
"eslint.enable": {
"scope": "resource",
"type": "boolean",
"default": true,
"description": "Controls whether eslint is enabled or not.",
"deprecationMessage": "This setting is deprecated. Disable ESLint using the extensions viewlet."
},
"eslint.packageManager": {
"scope": "resource",
"type": "string",
"enum": [
"npm",
"yarn",
"pnpm"
],
"default": "npm",
"description": "The package manager you use to install node modules."
},
"eslint.alwaysShowStatus": {
"type": "boolean",
"default": false,
"description": "Always show the ESlint status bar item.",
"scope": "window"
},
"eslint.nodeEnv": {
"scope": "resource",
"type": [
"string",
"null"
],
"default": null,
"description": "The value of NODE_ENV to use when running eslint tasks."
},
"eslint.nodePath": {
"scope": "machine-overridable",
"type": [
"string",
"null"
],
"default": null,
"description": "A path added to NODE_PATH when resolving the eslint module."
},
"eslint.options": {
"scope": "resource",
"type": "object",
"default": {},
"description": "The eslint options object to provide args normally passed to eslint when executed from a command line (see http://eslint.org/docs/developer-guide/nodejs-api#cliengine)."
},
"eslint.trace.server": {
"scope": "window",
"anyOf": [
{
"type": "string",
"enum": [
"off",
"messages",
"verbose"
],
"default": "off"
},
{
"type": "object",
"properties": {
"verbosity": {
"type": "string",
"enum": [
"off",
"messages",
"verbose"
],
"default": "off"
},
"format": {
"type": "string",
"enum": [
"text",
"json"
],
"default": "text"
}
}
}
],
"default": "off",
"description": "Traces the communication between VSCode and the eslint linter service."
},
"eslint.run": {
"scope": "resource",
"type": "string",
"enum": [
"onSave",
"onType"
],
"default": "onType",
"description": "Run the linter on save (onSave) or on type (onType)"
},
"eslint.autoFixOnSave": {
"scope": "resource",
"type": "boolean",
"default": false,
"description": "Turns auto fix on save on or off.",
"deprecationMessage": "The setting is deprecated. Use editor.codeActionsOnSave instead with a source.fixAll.eslint member."
},
"eslint.quiet": {
"scope": "resource",
"type": "boolean",
"default": false,
"description": "Turns on quiet mode, which ignores warnings."
},
"eslint.onIgnoredFiles": {
"scope": "resource",
"type": "string",
"enum": [
"warn",
"off"
],
"default": "off",
"description": "Whether ESLint should issue a warning on ignored files."
},
"eslint.migration.2_x": {
"scope": "application",
"type": "string",
"enum": [
"off",
"on"
],
"default": "on",
"description": "Whether ESlint should migrate auto fix on save settings."
},
"eslint.workingDirectories": {
"scope": "resource",
"type": "array",
"items": {
"anyOf": [
{
"type": "string"
},
{
"type": "object",
"properties": {
"mode": {
"type": "string",
"enum": [
"auto",
"location"
],
"default": "location"
}
},
"required": [
"mode"
]
},
{
"type": "object",
"properties": {
"directory": {
"type": "string",
"description": "The working directory to use if a file's path starts with this directory."
},
"changeProcessCWD": {
"type": "boolean",
"description": "Whether the process's cwd should be changed as well."
}
},
"deprecationMessage": "Use the new !cwd form.",
"required": [
"directory"
]
},
{
"type": "object",
"properties": {
"directory": {
"type": "string",
"description": "The working directory to use if a file's path starts with this directory."
},
"!cwd": {
"type": "boolean",
"description": "Set to true if ESLint shouldn't change the working directory."
}
},
"required": [
"directory"
]
},
{
"type": "object",
"properties": {
"pattern": {
"type": "string",
"description": "A glob pattern to match a working directory."
},
"!cwd": {
"type": "boolean",
"description": "Set to true if ESLint shouldn't change the working directory."
}
},
"required": [
"pattern"
]
}
]
}
},
"eslint.validate": {
"scope": "resource",
"type": "array",
"items": {
"anyOf": [
{
"type": "string"
},
{
"type": "object",
"properties": {
"language": {
"type": "string",
"description": "The language id to be validated by ESLint."
},
"autoFix": {
"type": "boolean",
"description": "Whether auto fixes are provided for the language."
}
},
"deprecationMessage": "Auto Fix is enabled by default. Use the single string form."
}
]
},
"description": "An array of language ids which should be validated by ESLint. If not installed ESLint will show an error."
},
"eslint.probe": {
"scope": "resource",
"type": "array",
"items": {
"type": "string"
},
"default": [
"javascript",
"javascriptreact",
"typescript",
"typescriptreact",
"html",
"vue",
"markdown"
],
"description": "An array of language ids for which the extension should probe if support is installed."
},
"eslint.provideLintTask": {
"scope": "resource",
"type": "boolean",
"default": false,
"deprecationMessage": "This option is deprecated. Use eslint.lintTask.enable instead.",
"description": "Controls whether a task for linting the whole workspace will be available."
},
"eslint.lintTask.enable": {
"scope": "resource",
"type": "boolean",
"default": false,
"description": "Controls whether a task for linting the whole workspace will be available."
},
"eslint.lintTask.options": {
"scope": "resource",
"type": "string",
"default": ".",
"description": "Command line options applied when running the task for linting the whole workspace (see https://eslint.org/docs/user-guide/command-line-interface)."
},
"eslint.runtime": {
"scope": "machine-overridable",
"type": [
"string",
"null"
],
"default": null,
"markdownDescription": "The location of the node binary to run ESLint under.\n\n- When specified as a user/machine setting, the Node version from `eslint.runtime` automatically replaces the built-in version.\n- When specified as a workspace setting, `eslint.runtime` allows you to switch to use that version with the `ESLint: Select Node version` command."
},
"eslint.debug": {
"scope": "window",
"type": "boolean",
"default": false,
"description": "Enables ESLint debug mode (same as --debug on the command line)"
},
"eslint.codeAction.disableRuleComment": {
"scope": "resource",
"type": "object",
"default": {
"enable": true,
"location": "separateLine"
},
"properties": {
"enable": {
"type": "boolean",
"default": true,
"description": "Show the disable code actions."
},
"location": {
"type": "string",
"enum": [
"separateLine",
"sameLine"
],
"default": "separateLine",
"description": "Configure the disable rule code action to insert the comment on the same line or a new line."
}
},
"additionalProperties": false
},
"eslint.codeAction.showDocumentation": {
"scope": "resource",
"type": "object",
"default": {
"enable": true
},
"properties": {
"enable": {
"type": "boolean",
"default": true,
"description": "Show the documentation code actions."
}
},
"additionalProperties": false
},
"eslint.codeActionsOnSave.mode": {
"scope": "resource",
"type": "string",
"enum": [
"all",
"problems"
],
"enumDescriptions": [
"Fixes all possible problems in the file. This option might take some time.",
"Only fixes reported problems that have non overlapping textual edits. This options runs a lot faster."
],
"default": "all",
"description": "Specifies the code action mode. Possible values are 'all' and 'problems'."
},
"eslint.format.enable": {
"scope": "resource",
"type": "boolean",
"default": false,
"description": "Enables ESLint as a formatter."
},
"eslint.rules.customizations": {
"description": "Override the severity of one or more rules reported by this extension, regardless of the project's ESLint config. Use globs to apply default severities for multiple rules.",
"items": {
"properties": {
"severity": {
"enum": [
"downgrade",
"error",
"info",
"default",
"upgrade",
"warn",
"off"
],
"type": "string"
},
"rule": {
"type": "string"
}
},
"type": "object"
},
"scope": "resource",
"type": "array"
}
}
},
"commands": [
{
"title": "Fix all auto-fixable Problems",
"category": "ESLint",
"command": "eslint.executeAutofix"
},
{
"title": "Create ESLint configuration",
"category": "ESLint",
"command": "eslint.createConfig"
},
{
"title": "Show Output Channel",
"category": "ESLint",
"command": "eslint.showOutputChannel"
},
{
"title": "Migrate Settings",
"category": "ESLint",
"command": "eslint.migrateSettings"
},
{
"title": "Restart ESLint Server",
"category": "ESLint",
"command": "eslint.restart"
}
],
"taskDefinitions": [
{
"type": "eslint"
}
],
"jsonValidation": [
{
"fileMatch": ".eslintrc",
"url": "https://json.schemastore.org/eslintrc"
},
{
"fileMatch": ".eslintrc.json",
"url": "https://json.schemastore.org/eslintrc"
},
{
"fileMatch": "package.json",
"url": "./package-json-schema.json"
}
],
"languages": [
{
"id": "ignore",
"extensions": [
".eslintignore"
]
},
{
"id": "jsonc",
"filenames": [
".eslintrc.json"
]
}
]
},
"scripts": {
"vscode:prepublish": "npm run webpack",
"webpack": "npm run clean && webpack --mode production --config ./client/webpack.config.js && webpack --mode production --config ./server/webpack.config.js",
"webpack:dev": "npm run clean && webpack --mode none --config ./client/webpack.config.js && webpack --mode none --config ./server/webpack.config.js",
"compile": "tsc -b",
"compile:client": "tsc -b ./client/tsconfig.json",
"compile:server": "tsc -b ./server/tsconfig.json",
"watch": "tsc -b -w",
"lint": "npm run lint:client && npm run lint:server",
"lint:client": "eslint --config ./client/.eslintrc.json ./client/src/*.ts",
"lint:server": "eslint --config ./server/.eslintrc.json ./server/src/*.ts",
"clean": "rimraf client/out && rimraf server/out",
"postinstall": "cd client && npm install && cd ../server && npm install && cd .."
},
"devDependencies": {
"@types/mocha": "^8.0.4",
"@types/node": "^14.14.31",
"@typescript-eslint/eslint-plugin": "^4.26.1",
"@typescript-eslint/parser": "^4.26.1",
"eslint": "^7.28.0",
"merge-options": "^3.0.4",
"mocha": "^8.2.1",
"rimraf": "^3.0.2",
"ts-loader": "^8.0.11",
"typescript": "^4.1.2",
"webpack": "^5.10.0",
"webpack-cli": "^4.2.0"
},
"__metadata": {
"id": "583b2b34-2c1e-4634-8c0b-0b82e283ea3a",
"publisherId": "29859a75-d81b-4f0e-8578-2c80ecee6f99",
"publisherDisplayName": "Dirk Baeumer",
"installedTimestamp": 1627023522292
}
}

2
.vscode/extensions/dbaeumer.vscode-eslint-2.1.23/server/out/eslintServer.js vendored Normal file
View file

File diff suppressed because one or more lines are too long

23
.vscode/extensions/dbaeumer.vscode-eslint-2.1.23/server/package.json vendored Normal file
View file

@ -0,0 +1,23 @@
{
"name": "eslint-server",
"version": "2.1.20",
"private": true,
"author": "Microsoft Corporation",
"license": "MIT",
"repository": {
"type": "git",
"url": "https://github.com/Microsoft/vscode-eslint.git"
},
"bugs": {
"url": "https://github.com/Microsoft/vscode-eslint/issues"
},
"engines": {
"node": "*"
},
"dependencies": {
"vscode-languageserver": "7.0.0",
"vscode-languageserver-textdocument": "1.0.1",
"vscode-uri": "^2.1.2"
},
"scripts": {}
}