@ionic/angular 7.6.2-dev.11702957417.1622fcc0 → 7.6.2-dev.11703182244.1165aeec

package/test/apps/ng14/node_modules/ts-node/README.md

@@ -1,302 +0,0 @@
-# ![TypeScript Node](logo.svg?sanitize=true)
-
-[![NPM version][npm-image]][npm-url]
-[![NPM downloads][downloads-image]][downloads-url]
-[![Build status][travis-image]][travis-url]
-[![Test coverage][coveralls-image]][coveralls-url]
-
-> TypeScript execution and REPL for node.js, with source map support. **Works with `typescript@>=2.7`**.
-
-### *Experimental ESM support*
-
-Native ESM support is currently experimental. For usage, limitations, and to provide feedback, see [#1007](https://github.com/TypeStrong/ts-node/issues/1007).
-
-## Installation
-
-```sh
-# Locally in your project.
-npm install -D typescript
-npm install -D ts-node
-
-# Or globally with TypeScript.
-npm install -g typescript
-npm install -g ts-node
-```
-
-**Tip:** Installing modules locally allows you to control and share the versions through `package.json`. TS Node will always resolve the compiler from `cwd` before checking relative to its own installation.
-
-## Usage
-
-### Shell
-
-```sh
-# Execute a script as `node` + `tsc`.
-ts-node script.ts
-
-# Starts a TypeScript REPL.
-ts-node
-
-# Execute code with TypeScript.
-ts-node -e 'console.log("Hello, world!")'
-
-# Execute, and print, code with TypeScript.
-ts-node -p -e '"Hello, world!"'
-
-# Pipe scripts to execute with TypeScript.
-echo 'console.log("Hello, world!")' | ts-node
-
-# Equivalent to ts-node --script-mode
-ts-node-script scripts.ts
-
-# Equivalent to ts-node --transpile-only
-ts-node-transpile-only scripts.ts
-```
-
-![TypeScript REPL](https://github.com/TypeStrong/ts-node/raw/master/screenshot.png)
-
-### Shebang
-
-```typescript
-#!/usr/bin/env ts-node-script
-
-console.log("Hello, world!")
-```
-
-`ts-node-script` is recommended because it enables `--script-mode`, discovering `tsconfig.json` relative to the script's location instead of `process.cwd()`.  This makes scripts more portable.
-
-Passing CLI arguments via shebang is allowed on Mac but not Linux.  For example, the following will fail on Linux:
-
-```
-#!/usr/bin/env ts-node --script-mode --transpile-only --files
-// This shebang is not portable.  It only works on Mac
-```
-
-### Programmatic
-
-You can require `ts-node` and register the loader for future requires by using `require('ts-node').register({ /* options */ })`. You can also use file shortcuts - `node -r ts-node/register` or `node -r ts-node/register/transpile-only` - depending on your preferences.
-
-**Note:** If you need to use advanced node.js CLI arguments (e.g. `--inspect`), use them with `node -r ts-node/register` instead of the `ts-node` CLI.
-
-#### Developers
-
-**TS Node** exports a `create()` function that can be used to initialize a TypeScript compiler that isn't registered to `require.extensions`, and it uses the same code as `register`.
-
-### Mocha
-
-Mocha 6
-
-```sh
-mocha --require ts-node/register --watch-extensions ts,tsx "test/**/*.{ts,tsx}" [...args]
-```
-
-**Note:** `--watch-extensions` is only used in `--watch` mode.
-
-Mocha 7
-
-```sh
-mocha --require ts-node/register --extensions ts,tsx --watch --watch-files src 'tests/**/*.{ts,tsx}' [...args]
-```
-
-### Tape
-
-```sh
-ts-node node_modules/tape/bin/tape [...args]
-```
-
-### Gulp
-
-```sh
-# Create a `gulpfile.ts` and run `gulp`.
-gulp
-```
-
-### Visual Studio Code
-
-Create a new node.js configuration, add `-r ts-node/register` to node args and move the `program` to the `args` list (so VS Code doesn't look for `outFiles`).
-
-```json
-{
-    "type": "node",
-    "request": "launch",
-    "name": "Launch Program",
-    "runtimeArgs": [
-        "-r",
-        "ts-node/register"
-    ],
-    "args": [
-        "${workspaceFolder}/index.ts"
-    ]
-}
-```
-
-**Note:** If you are using the `--project <tsconfig.json>` command line argument as per the [Configuration Options](#configuration-options), and want to apply this same behavior when launching in VS Code, add an "env" key into the launch configuration: `"env": { "TS_NODE_PROJECT": "<tsconfig.json>" }`.
-
-### IntelliJ (and WebStorm)
-
-Create a new Node.js configuration and add `-r ts-node/register` to "Node parameters."
-
-**Note:** If you are using the `--project <tsconfig.json>` command line argument as per the [Configuration Options](#configuration-options), and want to apply this same behavior when launching in IntelliJ, specify under "Environment Variables": `TS_NODE_PROJECT=<tsconfig.json>`.
-
-## How It Works
-
-**TypeScript Node** works by registering the TypeScript compiler for `.tsx?` and `.jsx?` (when `allowJs == true`) extensions. When node.js has an extension registered (via `require.extensions`), it will use the extension internally for module resolution. When an extension is unknown to node.js, it handles the file as `.js` (JavaScript). By default, **TypeScript Node** avoids compiling files in `/node_modules/` for three reasons:
-
-1. Modules should always be published in a format node.js can consume
-2. Transpiling the entire dependency tree will make your project slower
-3. Differing behaviours between TypeScript and node.js (e.g. ES2015 modules) can result in a project that works until you decide to support a feature natively from node.js
-
-**P.S.** This means if you don't register an extension, it is compiled as JavaScript. When `ts-node` is used with `allowJs`, JavaScript files are transpiled using the TypeScript compiler.
-
-## Loading `tsconfig.json`
-
-**Typescript Node** loads `tsconfig.json` automatically. Use `--skip-project` to skip loading the `tsconfig.json`.
-
-It is resolved relative to `--dir` using [the same search behavior as `tsc`](https://www.typescriptlang.org/docs/handbook/tsconfig-json.html).  In `--script-mode`, this is the directory containing the script.  Otherwise it is resolved relative to `process.cwd()`, which matches the behavior of `tsc`.
-
-Use `--project` to specify the path to your `tsconfig.json`, ignoring `--dir`.
-
-**Tip**: You can use `ts-node` together with [tsconfig-paths](https://www.npmjs.com/package/tsconfig-paths) to load modules according to the `paths` section in `tsconfig.json`.
-
-## Configuration Options
-
-You can set options by passing them before the script path, via programmatic usage, via `tsconfig.json`, or via environment variables.
-
-```sh
-ts-node --compiler ntypescript --project src/tsconfig.json hello-world.ts
-```
-
-**Note:** [`ntypescript`](https://github.com/TypeStrong/ntypescript#readme) is an example of a TypeScript-compatible `compiler`.
-
-### CLI Options
-
-`ts-node` supports `--print` (`-p`), `--eval` (`-e`), `--require` (`-r`) and `--interactive` (`-i`) similar to the [node.js CLI options](https://nodejs.org/api/cli.html).
-
-* `-h, --help` Prints the help text
-* `-v, --version` Prints the version. `-vv` prints node and typescript compiler versions, too
-* `-s, --script-mode` Resolve config relative to the directory of the passed script instead of the current directory. Changes default of `--dir`
-
-### CLI and Programmatic Options
-
-_The name of the environment variable and the option's default value are denoted in parentheses._
-
-* `-T, --transpile-only` Use TypeScript's faster `transpileModule` (`TS_NODE_TRANSPILE_ONLY`, default: `false`)
-* `-H, --compiler-host` Use TypeScript's compiler host API (`TS_NODE_COMPILER_HOST`, default: `false`)
-* `-I, --ignore [pattern]` Override the path patterns to skip compilation (`TS_NODE_IGNORE`, default: `/node_modules/`)
-* `-P, --project [path]` Path to TypeScript JSON project file (`TS_NODE_PROJECT`)
-* `-C, --compiler [name]` Specify a custom TypeScript compiler (`TS_NODE_COMPILER`, default: `typescript`)
-* `-D, --ignore-diagnostics [code]` Ignore TypeScript warnings by diagnostic code (`TS_NODE_IGNORE_DIAGNOSTICS`)
-* `-O, --compiler-options [opts]` JSON object to merge with compiler options (`TS_NODE_COMPILER_OPTIONS`)
-* `--dir` Specify working directory for config resolution (`TS_NODE_CWD`, default: `process.cwd()`, or `dirname(scriptPath)` if `--script-mode`)
-* `--scope` Scope compiler to files within `cwd` (`TS_NODE_SCOPE`, default: `false`)
-* `--files` Load `files`, `include` and `exclude` from `tsconfig.json` on startup (`TS_NODE_FILES`, default: `false`)
-* `--pretty` Use pretty diagnostic formatter (`TS_NODE_PRETTY`, default: `false`)
-* `--skip-project` Skip project config resolution and loading (`TS_NODE_SKIP_PROJECT`, default: `false`)
-* `--skip-ignore` Skip ignore checks (`TS_NODE_SKIP_IGNORE`, default: `false`)
-* `--emit` Emit output files into `.ts-node` directory (`TS_NODE_EMIT`, default: `false`)
-* `--prefer-ts-exts` Re-order file extensions so that TypeScript imports are preferred (`TS_NODE_PREFER_TS_EXTS`, default: `false`)
-* `--log-error` Logs TypeScript errors to stderr instead of throwing exceptions (`TS_NODE_LOG_ERROR`, default: `false`)
-
-### Programmatic-only Options
-
-* `transformers` `_ts.CustomTransformers | ((p: _ts.Program) => _ts.CustomTransformers)`: An object with transformers or a function that accepts a program and returns an transformers object to pass to TypeScript. Function isn't available with `transpileOnly` flag
-* `readFile`: Custom TypeScript-compatible file reading function
-* `fileExists`: Custom TypeScript-compatible file existence function
-
-### Options via tsconfig.json
-
-Most options can be specified by a `"ts-node"` object in `tsconfig.json` using their programmatic, camelCase names. For example, to enable `--transpile-only`:
-
-```json
-// tsconfig.json
-{
-  "ts-node": {
-    "transpileOnly": true
-  },
-  "compilerOptions": {}
-}
-```
-
-Our bundled [JSON schema](https://unpkg.com/browse/ts-node@8.8.2/tsconfig.schema.json) lists all compatible options.
-
-## SyntaxError
-
-Any error that is not a `TSError` is from node.js (e.g. `SyntaxError`), and cannot be fixed by TypeScript or `ts-node`. These are runtime issues with your code.
-
-### Import Statements
-
-Current node.js stable releases do not support ES modules. Additionally, `ts-node` does not have the required hooks into node.js to support ES modules. You will need to set `"module": "commonjs"` in your `tsconfig.json` for your code to work.
-
-## Help! My Types Are Missing!
-
-**TypeScript Node** does _not_ use `files`, `include` or `exclude`, by default. This is because a large majority projects do not use all of the files in a project directory (e.g. `Gulpfile.ts`, runtime vs tests) and parsing every file for types slows startup time. Instead, `ts-node` starts with the script file (e.g. `ts-node index.ts`) and TypeScript resolves dependencies based on imports and references.
-
-For global definitions, you can use the `typeRoots` compiler option.  This requires that your type definitions be structured as type packages (not loose TypeScript definition files). More details on how this works can be found in the [TypeScript Handbook](https://www.typescriptlang.org/docs/handbook/tsconfig-json.html#types-typeroots-and-types).
-
-Example `tsconfig.json`:
-
-```json
-{
-  "compilerOptions": {
-    "typeRoots" : ["./node_modules/@types", "./typings"]
-  }
-}
-```
-
-Example project structure:
-
-```text
-<project_root>/
--- tsconfig.json
--- typings/
-  -- <module_name>/
-    -- index.d.ts
-```
-
-Example module declaration file:
-
-```typescript
-declare module '<module_name>' {
-    // module definitions go here
-}
-```
-
-For module definitions, you can use [`paths`](https://www.typescriptlang.org/docs/handbook/module-resolution.html#path-mapping):
-
-```json
-{
-  "compilerOptions": {
-    "baseUrl": ".",
-    "paths": {
-      "custom-module-type": ["types/custom-module-type"]
-    }
-  }
-}
-```
-
-An alternative approach for definitions of third-party libraries are [triple-slash directives](https://www.typescriptlang.org/docs/handbook/triple-slash-directives.html). This may be helpful if you prefer not to change your TypeScript `compilerOptions` or structure your custom type definitions when using `typeRoots`. Below is an example of the triple-slash directive as a relative path within your project:
-
-```typescript
-/// <reference types="./types/untyped_js_lib" />
-import UntypedJsLib from "untyped_js_lib"
-```
-
-**Tip:** If you _must_ use `files`, `include`, or `exclude`, enable `--files` flags or set `TS_NODE_FILES=true`.
-
-## Watching and Restarting
-
-**TypeScript Node** compiles source code via `require()`, watching files and code reloads are out of scope for the project. If you want to restart the `ts-node` process on file change, existing node.js tools such as [nodemon](https://github.com/remy/nodemon), [onchange](https://github.com/Qard/onchange) and [node-dev](https://github.com/fgnass/node-dev) work.
-
-There's also [`ts-node-dev`](https://github.com/whitecolor/ts-node-dev), a modified version of [`node-dev`](https://github.com/fgnass/node-dev) using `ts-node` for compilation and won't restart the process on file change.
-
-## License
-
-MIT
-
-[npm-image]: https://img.shields.io/npm/v/ts-node.svg?style=flat
-[npm-url]: https://npmjs.org/package/ts-node
-[downloads-image]: https://img.shields.io/npm/dm/ts-node.svg?style=flat
-[downloads-url]: https://npmjs.org/package/ts-node
-[travis-image]: https://img.shields.io/travis/TypeStrong/ts-node.svg?style=flat
-[travis-url]: https://travis-ci.org/TypeStrong/ts-node
-[coveralls-image]: https://img.shields.io/coveralls/TypeStrong/ts-node.svg?style=flat
-[coveralls-url]: https://coveralls.io/r/TypeStrong/ts-node?branch=master

package/test/apps/ng14/node_modules/tslib/README.md

@@ -1,164 +0,0 @@
-# tslib
-
-This is a runtime library for [TypeScript](https://www.typescriptlang.org/) that contains all of the TypeScript helper functions.
-
-This library is primarily used by the `--importHelpers` flag in TypeScript.
-When using `--importHelpers`, a module that uses helper functions like `__extends` and `__assign` in the following emitted file:
-
-```ts
-var __assign = (this && this.__assign) || Object.assign || function(t) {
-    for (var s, i = 1, n = arguments.length; i < n; i++) {
-        s = arguments[i];
-        for (var p in s) if (Object.prototype.hasOwnProperty.call(s, p))
-            t[p] = s[p];
-    }
-    return t;
-};
-exports.x = {};
-exports.y = __assign({}, exports.x);
-
-```
-
-will instead be emitted as something like the following:
-
-```ts
-var tslib_1 = require("tslib");
-exports.x = {};
-exports.y = tslib_1.__assign({}, exports.x);
-```
-
-Because this can avoid duplicate declarations of things like `__extends`, `__assign`, etc., this means delivering users smaller files on average, as well as less runtime overhead.
-For optimized bundles with TypeScript, you should absolutely consider using `tslib` and `--importHelpers`.
-
-# Installing
-
-For the latest stable version, run:
-
-## npm
-
-```sh
-# TypeScript 3.9.2 or later
-npm install tslib
-
-# TypeScript 3.8.4 or earlier
-npm install tslib@^1
-
-# TypeScript 2.3.2 or earlier
-npm install tslib@1.6.1
-```
-
-## yarn
-
-```sh
-# TypeScript 3.9.2 or later
-yarn add tslib
-
-# TypeScript 3.8.4 or earlier
-yarn add tslib@^1
-
-# TypeScript 2.3.2 or earlier
-yarn add tslib@1.6.1
-```
-
-## bower
-
-```sh
-# TypeScript 3.9.2 or later
-bower install tslib
-
-# TypeScript 3.8.4 or earlier
-bower install tslib@^1
-
-# TypeScript 2.3.2 or earlier
-bower install tslib@1.6.1
-```
-
-## JSPM
-
-```sh
-# TypeScript 3.9.2 or later
-jspm install tslib
-
-# TypeScript 3.8.4 or earlier
-jspm install tslib@^1
-
-# TypeScript 2.3.2 or earlier
-jspm install tslib@1.6.1
-```
-
-# Usage
-
-Set the `importHelpers` compiler option on the command line:
-
-```
-tsc --importHelpers file.ts
-```
-
-or in your tsconfig.json:
-
-```json
-{
-    "compilerOptions": {
-        "importHelpers": true
-    }
-}
-```
-
-#### For bower and JSPM users
-
-You will need to add a `paths` mapping for `tslib`, e.g. For Bower users:
-
-```json
-{
-    "compilerOptions": {
-        "module": "amd",
-        "importHelpers": true,
-        "baseUrl": "./",
-        "paths": {
-            "tslib" : ["bower_components/tslib/tslib.d.ts"]
-        }
-    }
-}
-```
-
-For JSPM users:
-
-```json
-{
-    "compilerOptions": {
-        "module": "system",
-        "importHelpers": true,
-        "baseUrl": "./",
-        "paths": {
-            "tslib" : ["jspm_packages/npm/tslib@2.x.y/tslib.d.ts"]
-        }
-    }
-}
-```
-
-## Deployment
-
-- Choose your new version number
-- Set it in `package.json` and `bower.json`
-- Create a tag: `git tag [version]`
-- Push the tag: `git push --tags`
-- Create a [release in GitHub](https://github.com/microsoft/tslib/releases)
-- Run the [publish to npm](https://github.com/microsoft/tslib/actions?query=workflow%3A%22Publish+to+NPM%22) workflow
-
-Done.
-
-# Contribute
-
-There are many ways to [contribute](https://github.com/Microsoft/TypeScript/blob/master/CONTRIBUTING.md) to TypeScript.
-
-* [Submit bugs](https://github.com/Microsoft/TypeScript/issues) and help us verify fixes as they are checked in.
-* Review the [source code changes](https://github.com/Microsoft/TypeScript/pulls).
-* Engage with other TypeScript users and developers on [StackOverflow](http://stackoverflow.com/questions/tagged/typescript).
-* Join the [#typescript](http://twitter.com/#!/search/realtime/%23typescript) discussion on Twitter.
-* [Contribute bug fixes](https://github.com/Microsoft/TypeScript/blob/master/CONTRIBUTING.md).
-
-# Documentation
-
-* [Quick tutorial](http://www.typescriptlang.org/Tutorial)
-* [Programming handbook](http://www.typescriptlang.org/Handbook)
-* [Homepage](http://www.typescriptlang.org/)

package/test/apps/ng14/node_modules/typescript/README.md

@@ -1,104 +0,0 @@
-
-# TypeScript
-
-[![GitHub Actions CI](https://github.com/microsoft/TypeScript/workflows/CI/badge.svg)](https://github.com/microsoft/TypeScript/actions?query=workflow%3ACI)
-[![Devops Build Status](https://dev.azure.com/typescript/TypeScript/_apis/build/status/Typescript/node10)](https://dev.azure.com/typescript/TypeScript/_build?definitionId=7)
-[![npm version](https://badge.fury.io/js/typescript.svg)](https://www.npmjs.com/package/typescript)
-[![Downloads](https://img.shields.io/npm/dm/typescript.svg)](https://www.npmjs.com/package/typescript)
-
-[TypeScript](https://www.typescriptlang.org/) is a language for application-scale JavaScript. TypeScript adds optional types to JavaScript that support tools for large-scale JavaScript applications for any browser, for any host, on any OS. TypeScript compiles to readable, standards-based JavaScript. Try it out at the [playground](https://www.typescriptlang.org/play/), and stay up to date via [our blog](https://blogs.msdn.microsoft.com/typescript) and [Twitter account](https://twitter.com/typescript).
-
-Find others who are using TypeScript at [our community page](https://www.typescriptlang.org/community/).
-
-## Installing
-
-For the latest stable version:
-
-```bash
-npm install -g typescript
-```
-
-For our nightly builds:
-
-```bash
-npm install -g typescript@next
-```
-
-## Contribute
-
-There are many ways to [contribute](https://github.com/microsoft/TypeScript/blob/main/CONTRIBUTING.md) to TypeScript.
-* [Submit bugs](https://github.com/microsoft/TypeScript/issues) and help us verify fixes as they are checked in.
-* Review the [source code changes](https://github.com/microsoft/TypeScript/pulls).
-* Engage with other TypeScript users and developers on [StackOverflow](https://stackoverflow.com/questions/tagged/typescript).
-* Help each other in the [TypeScript Community Discord](https://discord.gg/typescript).
-* Join the [#typescript](https://twitter.com/search?q=%23TypeScript) discussion on Twitter.
-* [Contribute bug fixes](https://github.com/microsoft/TypeScript/blob/main/CONTRIBUTING.md).
-* Read the archived language specification ([docx](https://github.com/microsoft/TypeScript/blob/main/doc/TypeScript%20Language%20Specification%20-%20ARCHIVED.docx?raw=true),
- [pdf](https://github.com/microsoft/TypeScript/blob/main/doc/TypeScript%20Language%20Specification%20-%20ARCHIVED.pdf?raw=true), [md](https://github.com/microsoft/TypeScript/blob/main/doc/spec-ARCHIVED.md)).
-
-This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see
-the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com)
-with any additional questions or comments.
-
-## Documentation
-
-*  [TypeScript in 5 minutes](https://www.typescriptlang.org/docs/handbook/typescript-in-5-minutes.html)
-*  [Programming handbook](https://www.typescriptlang.org/docs/handbook/intro.html)
-*  [Homepage](https://www.typescriptlang.org/)
-
-## Building
-
-In order to build the TypeScript compiler, ensure that you have [Git](https://git-scm.com/downloads) and [Node.js](https://nodejs.org/) installed.
-
-Clone a copy of the repo:
-
-```bash
-git clone https://github.com/microsoft/TypeScript.git
-```
-
-Change to the TypeScript directory:
-
-```bash
-cd TypeScript
-```
-
-Install [Gulp](https://gulpjs.com/) tools and dev dependencies:
-
-```bash
-npm install -g gulp
-npm ci
-```
-
-Use one of the following to build and test:
-
-```
-gulp local             # Build the compiler into built/local.
-gulp clean             # Delete the built compiler.
-gulp LKG               # Replace the last known good with the built one.
-                       # Bootstrapping step to be executed when the built compiler reaches a stable state.
-gulp tests             # Build the test infrastructure using the built compiler.
-gulp runtests          # Run tests using the built compiler and test infrastructure.
-                       # You can override the specific suite runner used or specify a test for this command.
-                       # Use --tests=<testPath> for a specific test and/or --runner=<runnerName> for a specific suite.
-                       # Valid runners include conformance, compiler, fourslash, project, user, and docker
-                       # The user and docker runners are extended test suite runners - the user runner
-                       # works on disk in the tests/cases/user directory, while the docker runner works in containers.
-                       # You'll need to have the docker executable in your system path for the docker runner to work.
-gulp runtests-parallel # Like runtests, but split across multiple threads. Uses a number of threads equal to the system
-                       # core count by default. Use --workers=<number> to adjust this.
-gulp baseline-accept   # This replaces the baseline test results with the results obtained from gulp runtests.
-gulp lint              # Runs eslint on the TypeScript source.
-gulp help              # List the above commands.
-```
-
-
-## Usage
-
-```bash
-node built/local/tsc.js hello.ts
-```
-
-
-## Roadmap
-
-For details on our planned features and future direction please refer to our [roadmap](https://github.com/microsoft/TypeScript/wiki/Roadmap).

package/test/apps/ng14/node_modules/typescript-eslint-language-service/README.md

@@ -1,77 +0,0 @@
-# typescript-eslint-language-service
-
-[![github actions](https://github.com/Quramy/typescript-eslint-language-service/workflows/build/badge.svg)](https://github.com/Quramy/typescript-eslint-language-service/actions)
-[![npm version](https://badge.fury.io/js/typescript-eslint-language-service.svg)](https://badge.fury.io/js/typescript-eslint-language-service)
-![deps](https://david-dm.org/quramy/typescript-eslint-language-service.svg)
-[![GitHub license](https://img.shields.io/badge/license-MIT-blue.svg)](https://raw.githubusercontent.com/Quramy/ts-graphql-plugin/master/LICENSE.txt)
-
-TypeScript language service plugin to check ESLint errors.
-
-![Screencast](https://raw.githubusercontent.com/Quramy/typescript-eslint-language-service/master/cast.gif)
-
-## Features
-
-- Report ESLint errors as TypeScript semantic diagnostics
-- Create code-fix for ESLint errors if they have fixer
-
-## Usage
-
-### Requirements (peer dependencies)
-
-- `typescript`
-- `@typescript-eslint/parser` >= 4.0.0
-- `@typescript-eslint/typescript-estree` >= 4.0.0
-- `eslint`
-
-### Install
-
-```sh
-npm install typescript-eslint-language-service -D
-```
-
-### Configure
-
-And configure `plugins` section in your tsconfig.json, for example:
-
-```json
-{
-  "compilerOptions": {
-    "module": "commonjs",
-    "target": "es5",
-    "plugins": [
-      {
-        "name": "typescript-eslint-language-service"
-      }
-    ]
-  }
-}
-```
-
-It's ready to go. Launch your TypeScript IDE.
-
-### Plugin options
-
-```ts
-type PluginOptions = {
-  name: "typescript-eslint-language-service";
-  watchDirs?: string[];
-};
-```
-
-#### `watchDirs`
-
-By default, this plugins watches only `.eslintrc.*` files that exist in your project root directory. If you want to watch other directories, add their names.
-
-### Tips
-
-- Set `TS_ESLINT_SERVICE_DISABLED` env parameter and restart your IDE to turn this plugin off.
-
-### If you use older version of `@typescript-eslint` packages
-
-- **If your @typescript-eslint tool's version is < 4.0.0, install `typescript-eslint-language-service@3.1.x`.**
-- **If your @typescript-eslint tool's version is <= 3.4.0, install `typescript-eslint-language-service@3.0.x`.**
-- **If your @typescript-eslint tool's version is <= 2.x.x, install `typescript-eslint-language-service@2.x.x`.**
-
-## LICENSE
-
-MIT