@ionic/angular 7.6.2-dev.11702926577.1a448647 → 7.6.2-dev.11702957417.1622fcc0

package/test/apps/ng15/node_modules/@typescript-eslint/parser/README.md

@@ -0,0 +1,265 @@
+<h1 align="center">TypeScript ESLint Parser</h1>
+
+<p align="center">An ESLint parser which leverages <a href="https://github.com/typescript-eslint/typescript-eslint/tree/master/packages/typescript-estree">TypeScript ESTree</a> to allow for ESLint to lint TypeScript source code.</p>
+
+<p align="center">
+    <img src="https://github.com/typescript-eslint/typescript-eslint/workflows/CI/badge.svg" alt="CI" />
+    <a href="https://www.npmjs.com/package/@typescript-eslint/parser"><img src="https://img.shields.io/npm/v/@typescript-eslint/parser.svg?style=flat-square" alt="NPM Version" /></a>
+    <a href="https://www.npmjs.com/package/@typescript-eslint/parser"><img src="https://img.shields.io/npm/dm/@typescript-eslint/parser.svg?style=flat-square" alt="NPM Downloads" /></a>
+</p>
+
+## Getting Started
+
+**[You can find our Getting Started docs here](../../docs/getting-started/linting/README.md)**
+
+These docs walk you through setting up ESLint, this parser, and our plugin. If you know what you're doing and just want to quick start, read on...
+
+## Quick-start
+
+### Installation
+
+```bash
+$ yarn add -D typescript @typescript-eslint/parser
+$ npm i --save-dev typescript @typescript-eslint/parser
+```
+
+### Usage
+
+In your ESLint configuration file, set the `parser` property:
+
+```json
+{
+  "parser": "@typescript-eslint/parser"
+}
+```
+
+There is sometimes an incorrect assumption that the parser itself is what does everything necessary to facilitate the use of ESLint with TypeScript. In actuality, it is the combination of the parser _and_ one or more plugins which allow you to maximize your usage of ESLint with TypeScript.
+
+For example, once this parser successfully produces an AST for the TypeScript source code, it might well contain some information which simply does not exist in a standard JavaScript context, such as the data for a TypeScript-specific construct, like an `interface`.
+
+The core rules built into ESLint, such as `indent` have no knowledge of such constructs, so it is impossible to expect them to work out of the box with them.
+
+Instead, you also need to make use of one more plugins which will add or extend rules with TypeScript-specific features.
+
+By far the most common case will be installing the [`@typescript-eslint/eslint-plugin`](https://github.com/typescript-eslint/typescript-eslint/tree/master/packages/eslint-plugin) plugin, but there are also other relevant options available such a [`@typescript-eslint/eslint-plugin-tslint`](https://github.com/typescript-eslint/typescript-eslint/tree/master/packages/eslint-plugin-tslint).
+
+## Configuration
+
+The following additional configuration options are available by specifying them in [`parserOptions`](https://eslint.org/docs/user-guide/configuring/language-options#specifying-parser-options) in your ESLint configuration file.
+
+```ts
+interface ParserOptions {
+  ecmaFeatures?: {
+    jsx?: boolean;
+    globalReturn?: boolean;
+  };
+  ecmaVersion?: number;
+
+  jsxPragma?: string;
+  jsxFragmentName?: string | null;
+  lib?: string[];
+
+  project?: string | string[];
+  projectFolderIgnoreList?: string[];
+  tsconfigRootDir?: string;
+  extraFileExtensions?: string[];
+  warnOnUnsupportedTypeScriptVersion?: boolean;
+
+  program?: import('typescript').Program;
+}
+```
+
+### `parserOptions.ecmaFeatures.jsx`
+
+Default `false`.
+
+Enable parsing JSX when `true`. More details can be found [here](https://www.typescriptlang.org/docs/handbook/jsx.html).
+
+**NOTE:** this setting does not affect known file types (`.js`, `.jsx`, `.ts`, `.tsx`, `.json`) because the TypeScript compiler has its own internal handling for known file extensions. The exact behavior is as follows:
+
+- if `parserOptions.project` is _not_ provided:
+  - `.js`, `.jsx`, `.tsx` files are parsed as if this is true.
+  - `.ts` files are parsed as if this is false.
+  - unknown extensions (`.md`, `.vue`) will respect this setting.
+- if `parserOptions.project` is provided (i.e. you are using rules with type information):
+  - `.js`, `.jsx`, `.tsx` files are parsed as if this is true.
+  - `.ts` files are parsed as if this is false.
+  - "unknown" extensions (`.md`, `.vue`) **are parsed as if this is false**.
+
+### `parserOptions.ecmaFeatures.globalReturn`
+
+Default `false`.
+
+This options allows you to tell the parser if you want to allow global `return` statements in your codebase.
+
+### `parserOptions.ecmaVersion`
+
+Default `2018`.
+
+Accepts any valid ECMAScript version number:
+
+- A version: es3, es5, es6, es7, es8, es9, es10, es11, ..., or
+- A year: es2015, es2016, es2017, es2018, es2019, es2020, ...
+
+The value **must** be a number - so do not include the `es` prefix.
+
+Specifies the version of ECMAScript syntax you want to use. This is used by the parser to determine how to perform scope analysis, and it affects the default
+
+### `parserOptions.jsxPragma`
+
+Default `'React'`
+
+The identifier that's used for JSX Elements creation (after transpilation).
+If you're using a library other than React (like `preact`), then you should change this value.
+
+This should not be a member expression - just the root identifier (i.e. use `"React"` instead of `"React.createElement"`).
+
+If you provide `parserOptions.project`, you do not need to set this, as it will automatically detected from the compiler.
+
+### `parserOptions.jsxFragmentName`
+
+Default `null`
+
+The identifier that's used for JSX fragment elements (after transpilation).
+If `null`, assumes transpilation will always use a member of the configured `jsxPragma`.
+This should not be a member expression - just the root identifier (i.e. use `"h"` instead of `"h.Fragment"`).
+
+If you provide `parserOptions.project`, you do not need to set this, as it will automatically detected from the compiler.
+
+### `parserOptions.lib`
+
+Default `['es2018']`
+
+For valid options, see the [TypeScript compiler options](https://www.typescriptlang.org/tsconfig#lib).
+
+Specifies the TypeScript `lib`s that are available. This is used by the scope analyser to ensure there are global variables declared for the types exposed by TypeScript.
+
+If you provide `parserOptions.project`, you do not need to set this, as it will automatically detected from the compiler.
+
+### `parserOptions.project`
+
+Default `undefined`.
+
+This option allows you to provide a path to your project's `tsconfig.json`. **This setting is required if you want to use rules which require type information**. Relative paths are interpreted relative to the current working directory if `tsconfigRootDir` is not set. If you intend on running ESLint from directories other than the project root, you should consider using `tsconfigRootDir`.
+
+- Accepted values:
+
+  ```js
+  // path
+  project: './tsconfig.json';
+
+  // glob pattern
+  project: './packages/**/tsconfig.json';
+
+  // array of paths and/or glob patterns
+  project: ['./packages/**/tsconfig.json', './separate-package/tsconfig.json'];
+  ```
+
+- If you use project references, TypeScript will not automatically use project references to resolve files. This means that you will have to add each referenced tsconfig to the `project` field either separately, or via a glob.
+
+- TypeScript will ignore files with duplicate filenames in the same folder (for example, `src/file.ts` and `src/file.js`). TypeScript purposely ignore all but one of the files, only keeping the one file with the highest priority extension (the extension priority order (from highest to lowest) is `.ts`, `.tsx`, `.d.ts`, `.js`, `.jsx`). For more info see #955.
+
+- Note that if this setting is specified and `createDefaultProgram` is not, you must only lint files that are included in the projects as defined by the provided `tsconfig.json` files. If your existing configuration does not include all of the files you would like to lint, you can create a separate `tsconfig.eslint.json` as follows:
+
+  ```jsonc
+  {
+    // extend your base config so you don't have to redefine your compilerOptions
+    "extends": "./tsconfig.json",
+    "include": [
+      "src/**/*.ts",
+      "test/**/*.ts",
+      "typings/**/*.ts",
+      // etc
+
+      // if you have a mixed JS/TS codebase, don't forget to include your JS files
+      "src/**/*.js"
+    ]
+  }
+  ```
+
+### `parserOptions.tsconfigRootDir`
+
+Default `undefined`.
+
+This option allows you to provide the root directory for relative tsconfig paths specified in the `project` option above.
+
+### `parserOptions.projectFolderIgnoreList`
+
+Default `["**/node_modules/**"]`.
+
+This option allows you to ignore folders from being included in your provided list of `project`s.
+This is useful if you have configured glob patterns, but want to make sure you ignore certain folders.
+
+It accepts an array of globs to exclude from the `project` globs.
+
+For example, by default it will ensure that a glob like `./**/tsconfig.json` will not match any `tsconfig`s within your `node_modules` folder (some npm packages do not exclude their source files from their published packages).
+
+### `parserOptions.extraFileExtensions`
+
+Default `undefined`.
+
+This option allows you to provide one or more additional file extensions which should be considered in the TypeScript Program compilation.
+The default extensions are `.ts`, `.tsx`, `.js`, and `.jsx`. Add extensions starting with `.`, followed by the file extension. E.g. for a `.vue` file use `"extraFileExtensions: [".vue"]`.
+
+### `parserOptions.warnOnUnsupportedTypeScriptVersion`
+
+Default `true`.
+
+This option allows you to toggle the warning that the parser will give you if you use a version of TypeScript which is not explicitly supported
+
+### `parserOptions.createDefaultProgram`
+
+Default `false`.
+
+This option allows you to request that when the `project` setting is specified, files will be allowed when not included in the projects defined by the provided `tsconfig.json` files. **Using this option will incur significant performance costs. This option is primarily included for backwards-compatibility.** See the **`project`** section above for more information.
+
+### `parserOptions.programs`
+
+Default `undefined`.
+
+This option allows you to programmatically provide an array of one or more instances of a TypeScript Program object that will provide type information to rules.
+This will override any programs that would have been computed from `parserOptions.project` or `parserOptions.createDefaultProgram`.
+All linted files must be part of the provided program(s).
+
+## Utilities
+
+### `createProgram(configFile, projectDirectory)`
+
+This serves as a utility method for users of the `parserOptions.programs` feature to create a TypeScript program instance from a config file.
+
+```ts
+declare function createProgram(
+  configFile: string,
+  projectDirectory?: string,
+): import('typescript').Program;
+```
+
+Example usage in .eslintrc.js:
+
+```js
+const parser = require('@typescript-eslint/parser');
+const programs = [parser.createProgram('tsconfig.json')];
+module.exports = {
+  parserOptions: {
+    programs,
+  },
+};
+```
+
+## Supported TypeScript Version
+
+Please see [`typescript-eslint`](https://github.com/typescript-eslint/typescript-eslint) for the supported TypeScript version.
+
+**Please ensure that you are using a supported version before submitting any issues/bug reports.**
+
+## Reporting Issues
+
+Please use the `@typescript-eslint/parser` issue template when creating your issue and fill out the information requested as best you can. This will really help us when looking into your issue.
+
+## License
+
+TypeScript ESLint Parser is licensed under a permissive BSD 2-clause license.
+
+## Contributing
+
+[See the contributing guide here](../../CONTRIBUTING.md)

package/test/apps/ng15/node_modules/concurrently/README.md

@@ -0,0 +1,315 @@
+# Concurrently
+
+[![Build Status](https://github.com/open-cli-tools/concurrently/workflows/Tests/badge.svg)](https://github.com/open-cli-tools/concurrently/actions?workflow=Tests) 
+[![Coverage Status](https://coveralls.io/repos/github/open-cli-tools/concurrently/badge.svg?branch=master)](https://coveralls.io/github/open-cli-tools/concurrently?branch=master)
+
+[![NPM Badge](https://nodei.co/npm/concurrently.png?downloads=true)](https://www.npmjs.com/package/concurrently)
+
+Run multiple commands concurrently.
+Like `npm run watch-js & npm run watch-less` but better.
+
+![](docs/demo.gif)
+
+**Table of contents**
+- [Concurrently](#concurrently)
+  - [Why](#why)
+  - [Install](#install)
+  - [Usage](#usage)
+  - [Programmatic Usage](#programmatic-usage)
+    - [`concurrently(commands[, options])`](#concurrentlycommands-options)
+  - [FAQ](#faq)
+
+## Why
+
+I like [task automation with npm](https://github.com/substack/blog/blob/master/npm_run.markdown)
+but the usual way to run multiple commands concurrently is
+`npm run watch-js & npm run watch-css`. That's fine but it's hard to keep
+on track of different outputs. Also if one process fails, others still keep running
+and you won't even notice the difference.
+
+Another option would be to just run all commands in separate terminals. I got
+tired of opening terminals and made **concurrently**.
+
+**Features:**
+
+* Cross platform (including Windows)
+* Output is easy to follow with prefixes
+* With `--kill-others` switch, all commands are killed if one dies
+* Spawns commands with [spawn-command](https://github.com/mmalecki/spawn-command)
+
+## Install
+
+The tool is written in Node.js, but you can use it to run **any** commands.
+
+```bash
+npm install -g concurrently
+```
+
+or if you are using it from npm scripts:
+
+```bash
+npm install concurrently --save
+```
+
+## Usage
+
+Remember to surround separate commands with quotes:
+```bash
+concurrently "command1 arg" "command2 arg"
+```
+
+Otherwise **concurrently** would try to run 4 separate commands:
+`command1`, `arg`, `command2`, `arg`.
+
+In package.json, escape quotes:
+
+```bash
+"start": "concurrently \"command1 arg\" \"command2 arg\""
+```
+
+NPM run commands can be shortened:
+
+```bash
+concurrently "npm:watch-js" "npm:watch-css" "npm:watch-node"
+
+# Equivalent to:
+concurrently -n watch-js,watch-css,watch-node "npm run watch-js" "npm run watch-css" "npm run watch-node"
+```
+
+NPM shortened commands also support wildcards. Given the following scripts in
+package.json:
+
+```javascript
+{
+    //...
+    "scripts": {
+        // ...
+        "watch-js": "...",
+        "watch-css": "...",
+        "watch-node": "...",
+        // ...
+    },
+    // ...
+}
+```
+
+```bash
+concurrently "npm:watch-*"
+
+# Equivalent to:
+concurrently -n js,css,node "npm run watch-js" "npm run watch-css" "npm run watch-node"
+
+# Any name provided for the wildcard command will be used as a prefix to the wildcard
+# part of the script name:
+concurrently -n w: npm:watch-*
+
+# Equivalent to:
+concurrently -n w:js,w:css,w:node "npm run watch-js" "npm run watch-css" "npm run watch-node"
+```
+
+Good frontend one-liner example [here](https://github.com/kimmobrunfeldt/dont-copy-paste-this-frontend-template/blob/5cd2bde719654941bdfc0a42c6f1b8e69ae79980/package.json#L9).
+
+Help:
+
+```
+
+concurrently [options] <command ...>
+
+General
+  -m, --max-processes   How many processes should run at once.
+                        New processes only spawn after all restart tries of a
+                        process.                                        [number]
+  -n, --names           List of custom names to be used in prefix template.
+                        Example names: "main,browser,server"            [string]
+      --name-separator  The character to split <names> on. Example usage:
+                        concurrently -n "styles|scripts|server" --name-separator
+                        "|"                                       [default: ","]
+  -r, --raw             Output only raw output of processes, disables
+                        prettifying and concurrently coloring.         [boolean]
+  -s, --success         Return exit code of zero or one based on the success or
+                        failure of the "first" child to terminate, the "last
+                        child", or succeed only if "all" child processes
+                        succeed.
+                              [choices: "first", "last", "all"] [default: "all"]
+      --no-color        Disables colors from logging                   [boolean]
+      --hide            Comma-separated list of processes to hide the output.
+                        The processes can be identified by their name or index.
+                                                          [string] [default: ""]
+
+Prefix styling
+  -p, --prefix            Prefix used in logging for each process.
+                          Possible values: index, pid, time, command, name,
+                          none, or a template. Example template: "{time}-{pid}"
+                         [string] [default: index or name (when --names is set)]
+  -c, --prefix-colors     Comma-separated list of chalk colors to use on
+                          prefixes. If there are more commands than colors, the
+                          last color will be repeated.
+                          - Available modifiers: reset, bold, dim, italic,
+                          underline, inverse, hidden, strikethrough
+                          - Available colors: black, red, green, yellow, blue,
+                          magenta, cyan, white, gray, or any hex values for
+                          colors, eg #23de43
+                          - Available background colors: bgBlack, bgRed,
+                          bgGreen, bgYellow, bgBlue, bgMagenta, bgCyan, bgWhite
+                          See https://www.npmjs.com/package/chalk for more
+                          information.            [string] [default: "reset"]
+  -l, --prefix-length     Limit how many characters of the command is displayed
+                          in prefix. The option can be used to shorten the
+                          prefix when it is set to "command"
+                                                          [number] [default: 10]
+  -t, --timestamp-format  Specify the timestamp in moment/date-fns format.
+                                   [string] [default: "yyyy-MM-dd HH:mm:ss.SSS"]
+
+Input handling
+  -i, --handle-input      Whether input should be forwarded to the child
+                          processes. See examples for more information.[boolean]
+  --default-input-target  Identifier for child process to which input on stdin
+                          should be sent if not specified at start of input.
+                          Can be either the index or the name of the process.
+                                                                    [default: 0]
+
+Killing other processes
+  -k, --kill-others      kill other processes if one exits or dies     [boolean]
+  --kill-others-on-fail  kill other processes if one exits with non zero status
+                         code                                          [boolean]
+
+Restarting
+      --restart-tries  How many times a process that died should restart.
+                       Negative numbers will make the process restart forever.
+                                                           [number] [default: 0]
+      --restart-after  Delay time to respawn the process, in milliseconds.
+                                                           [number] [default: 0]
+
+Options:
+  -h, --help         Show help                                         [boolean]
+  -v, -V, --version  Show version number                               [boolean]
+
+Examples:
+
+ - Output nothing more than stdout+stderr of child processes
+
+     $ concurrently --raw "npm run watch-less" "npm run watch-js"
+
+ - Normal output but without colors e.g. when logging to file
+
+     $ concurrently --no-color "grunt watch" "http-server" > log
+
+ - Custom prefix
+
+     $ concurrently --prefix "{time}-{pid}" "npm run watch" "http-server"
+
+ - Custom names and colored prefixes
+
+     $ concurrently --names "HTTP,WATCH" -c "bgBlue.bold,bgMagenta.bold"
+     "http-server" "npm run watch"
+
+ - Configuring via environment variables with CONCURRENTLY_ prefix
+
+     $ CONCURRENTLY_RAW=true CONCURRENTLY_KILL_OTHERS=true concurrently "echo hello" "echo world"
+
+ - Send input to default
+
+     $ concurrently --handle-input "nodemon" "npm run watch-js"
+     rs  # Sends rs command to nodemon process
+
+ - Send input to specific child identified by index
+
+     $ concurrently --handle-input "npm run watch-js" nodemon
+     1:rs
+
+ - Send input to specific child identified by name
+
+     $ concurrently --handle-input -n js,srv "npm run watch-js" nodemon
+     srv:rs
+
+ - Shortened NPM run commands
+
+     $ concurrently npm:watch-node npm:watch-js npm:watch-css
+
+ - Shortened NPM run command with wildcard (make sure to wrap it in quotes!)
+
+     $ concurrently "npm:watch-*"
+
+For more details, visit https://github.com/open-cli-tools/concurrently
+```
+
+## Programmatic Usage
+concurrently can be used programmatically by using the API documented below:
+
+### `concurrently(commands[, options])`
+
+- `commands`: an array of either strings (containing the commands to run) or objects
+  with the shape `{ command, name, prefixColor, env, cwd }`.
+
+- `options` (optional): an object containing any of the below:
+    - `cwd`: the working directory to be used by all commands. Can be overriden per command.
+    Default: `process.cwd()`.
+    - `defaultInputTarget`: the default input target when reading from `inputStream`.
+    Default: `0`.
+    - `handleInput`: when `true`, reads input from `process.stdin`.
+    - `inputStream`: a [`Readable` stream](https://nodejs.org/dist/latest-v10.x/docs/api/stream.html#stream_readable_streams)
+    to read the input from. Should only be used in the rare instance you would like to stream anything other than `process.stdin`. Overrides `handleInput`.
+    - `pauseInputStreamOnFinish`: by default, pauses the input stream (`process.stdin` when `handleInput` is enabled, or `inputStream` if provided) when all of the processes have finished. If you need to read from the input stream after `concurrently` has finished, set this to `false`. ([#252](https://github.com/kimmobrunfeldt/concurrently/issues/252)).
+    - `killOthers`: an array of exitting conditions that will cause a process to kill others.
+    Can contain any of `success` or `failure`.
+    - `maxProcesses`: how many processes should run at once.
+    - `outputStream`: a [`Writable` stream](https://nodejs.org/dist/latest-v10.x/docs/api/stream.html#stream_writable_streams)
+    to write logs to. Default: `process.stdout`.
+    - `prefix`: the prefix type to use when logging processes output.
+      Possible values: `index`, `pid`, `time`, `command`, `name`, `none`, or a template (eg `[{time} process: {pid}]`).
+      Default: the name of the process, or its index if no name is set.
+    - `prefixColors`: a list of colors as supported by [chalk](https://www.npmjs.com/package/chalk).
+      If concurrently would run more commands than there are colors, the last color is repeated.
+      Prefix colors specified per-command take precedence over this list.
+    - `prefixLength`: how many characters to show when prefixing with `command`. Default: `10`
+    - `raw`: whether raw mode should be used, meaning strictly process output will
+    be logged, without any prefixes, colouring or extra stuff.
+    - `successCondition`: the condition to consider the run was successful.
+    If `first`, only the first process to exit will make up the success of the run; if `last`, the last process that exits will determine whether the run succeeds.
+    Anything else means all processes should exit successfully.
+    - `restartTries`: how many attempts to restart a process that dies will be made. Default: `0`.
+    - `restartDelay`: how many milliseconds to wait between process restarts. Default: `0`.
+    - `timestampFormat`: a [date-fns format](https://date-fns.org/v2.0.1/docs/format)
+    to use when prefixing with `time`. Default: `yyyy-MM-dd HH:mm:ss.ZZZ`
+
+> Returns: a `Promise` that resolves if the run was successful (according to `successCondition` option),
+> or rejects, containing an array of objects with information for each command that has been run, in the order
+> that the commands terminated. The objects have the shape `{ command, index, exitCode, killed }`, where `command` is the object
+> passed in the `commands` array, `index` its index there and `killed` indicates if the process was killed as a result of
+> `killOthers`. Default values (empty strings or objects) are returned for the fields that were not specified.
+
+Example:
+
+```js
+const concurrently = require('concurrently');
+concurrently([
+    'npm:watch-*',
+    { command: 'nodemon', name: 'server' },
+    { command: 'deploy', name: 'deploy', env: { PUBLIC_KEY: '...' } },
+    { command: 'watch', name: 'watch', cwd: path.resolve(__dirname, 'scripts/watchers')}
+], {
+    prefix: 'name',
+    killOthers: ['failure', 'success'],
+    restartTries: 3,
+    cwd: path.resolve(__dirname, 'scripts'),
+}).then(success, failure);
+```
+
+## FAQ
+
+* Process exited with code *null*?
+
+    From [Node child_process documentation](http://nodejs.org/api/child_process.html#child_process_event_exit), `exit` event:
+
+    > This event is emitted after the child process ends. If the process
+    > terminated normally, code is the final exit code of the process,
+    > otherwise null. If the process terminated due to receipt of a signal,
+    > signal is the string name of the signal, otherwise null.
+
+
+    So *null* means the process didn't terminate normally. This will make **concurrent**
+    to return non-zero exit code too.
+
+* Does this work with the npm-replacements [yarn](https://github.com/yarnpkg/yarn) or [pnpm](https://pnpm.js.org/)?
+
+    Yes! In all examples above, you may replace "`npm`" with "`yarn`" or "`pnpm`".