less 3.10.1 → 3.11.1

package/packages/less/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-unnecessary-type-assertion.md

@@ -0,0 +1,69 @@
+# Warns if a type assertion does not change the type of an expression (no-unnecessary-type-assertion)
+
+This rule prohibits using a type assertion that does not change the type of an expression.
+
+## Rule Details
+
+This rule aims to prevent unnecessary type assertions.
+
+Examples of **incorrect** code for this rule:
+
+```ts
+const foo = 3;
+const bar = foo!;
+```
+
+```ts
+const foo = <3>3;
+```
+
+```ts
+type Foo = 3;
+const foo = <Foo>3;
+```
+
+```ts
+type Foo = 3;
+const foo = 3 as Foo;
+```
+
+```ts
+function foo(x: number): number {
+  return x!; // unnecessary non-null
+}
+```
+
+Examples of **correct** code for this rule:
+
+```ts
+const foo = <number>3;
+```
+
+```ts
+const foo = 3 as number;
+```
+
+```ts
+function foo(x: number | undefined): number {
+  return x!;
+}
+```
+
+### Options
+
+This rule optionally takes an object with a single property `typesToIgnore`, which can be set to a list of type names to ignore.
+
+For example, with `@typescript-eslint/no-unnecessary-type-assertion: ["error", { typesToIgnore: ['Foo'] }]`, the following is **correct** code":
+
+```ts
+type Foo = 3;
+const foo: Foo = 3;
+```
+
+## When Not To Use It
+
+If you don't care about having no-op type assertions in your code, then you can turn off this rule.
+
+## Related to
+
+- TSLint: ['no-unnecessary-type-assertion`](https://palantir.github.io/tslint/rules/no-unnecessary-type-assertion/)

package/packages/less/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-unused-vars.md

@@ -0,0 +1,305 @@
+# Disallow unused variables (no-unused-vars)
+
+Variables that are declared and not used anywhere in the code are most likely an error due to incomplete refactoring. Such variables take up space in the code and can lead to confusion by readers.
+
+## Rule Details
+
+This rule is aimed at eliminating unused variables, functions, and parameters of functions.
+
+A variable is considered to be used if any of the following are true:
+
+- It represents a function that is called (`doSomething()`)
+- It is read (`var y = x`)
+- It is passed into a function as an argument (`doSomething(x)`)
+- It is read inside of a function that is passed to another function (`doSomething(function() { foo(); })`)
+
+A variable is _not_ considered to be used if it is only ever assigned to (`var x = 5`) or declared.
+
+Examples of **incorrect** code for this rule:
+
+```js
+/*eslint no-unused-vars: "error"*/
+/*global some_unused_var*/
+
+// It checks variables you have defined as global
+some_unused_var = 42;
+
+var x;
+
+// Write-only variables are not considered as used.
+var y = 10;
+y = 5;
+
+// A read for a modification of itself is not considered as used.
+var z = 0;
+z = z + 1;
+
+// By default, unused arguments cause warnings.
+(function(foo) {
+  return 5;
+})();
+
+// Unused recursive functions also cause warnings.
+function fact(n) {
+  if (n < 2) return 1;
+  return n * fact(n - 1);
+}
+
+// When a function definition destructures an array, unused entries from the array also cause warnings.
+function getY([x, y]) {
+  return y;
+}
+```
+
+Examples of **correct** code for this rule:
+
+```js
+/*eslint no-unused-vars: "error"*/
+
+var x = 10;
+alert(x);
+
+// foo is considered used here
+myFunc(
+  function foo() {
+    // ...
+  }.bind(this),
+);
+
+(function(foo) {
+  return foo;
+})();
+
+var myFunc;
+myFunc = setTimeout(function() {
+  // myFunc is considered used
+  myFunc();
+}, 50);
+
+// Only the second argument from the descructured array is used.
+function getY([, y]) {
+  return y;
+}
+```
+
+### exported
+
+In environments outside of CommonJS or ECMAScript modules, you may use `var` to create a global variable that may be used by other scripts. You can use the `/* exported variableName */` comment block to indicate that this variable is being exported and therefore should not be considered unused.
+
+Note that `/* exported */` has no effect for any of the following:
+
+- when the environment is `node` or `commonjs`
+- when `parserOptions.sourceType` is `module`
+- when `ecmaFeatures.globalReturn` is `true`
+
+The line comment `// exported variableName` will not work as `exported` is not line-specific.
+
+Examples of **correct** code for `/* exported variableName */` operation:
+
+```js
+/* exported global_var */
+
+var global_var = 42;
+```
+
+## Options
+
+This rule takes one argument which can be a string or an object. The string settings are the same as those of the `vars` property (explained below).
+
+By default this rule is enabled with `all` option for variables and `after-used` for arguments.
+
+```CJSON
+{
+  "rules": {
+    // note you must disable the base rule as it can report incorrect errors
+    "no-unused-vars": "off",
+    "@typescript-eslint/no-unused-vars": ["error", {
+      "vars": "all",
+      "args": "after-used",
+      "ignoreRestSiblings": false
+    }]
+  }
+}
+```
+
+### vars
+
+The `vars` option has two settings:
+
+- `all` checks all variables for usage, including those in the global scope. This is the default setting.
+- `local` checks only that locally-declared variables are used but will allow global variables to be unused.
+
+#### vars: local
+
+Examples of **correct** code for the `{ "vars": "local" }` option:
+
+```js
+/*eslint no-unused-vars: ["error", { "vars": "local" }]*/
+/*global some_unused_var */
+
+some_unused_var = 42;
+```
+
+### varsIgnorePattern
+
+The `varsIgnorePattern` option specifies exceptions not to check for usage: variables whose names match a regexp pattern. For example, variables whose names contain `ignored` or `Ignored`.
+
+Examples of **correct** code for the `{ "varsIgnorePattern": "[iI]gnored" }` option:
+
+```js
+/*eslint no-unused-vars: ["error", { "varsIgnorePattern": "[iI]gnored" }]*/
+
+var firstVarIgnored = 1;
+var secondVar = 2;
+console.log(secondVar);
+```
+
+### args
+
+The `args` option has three settings:
+
+- `after-used` - unused positional arguments that occur before the last used argument will not be checked, but all named arguments and all positional arguments after the last used argument will be checked.
+- `all` - all named arguments must be used.
+- `none` - do not check arguments.
+
+#### args: after-used
+
+Examples of **incorrect** code for the default `{ "args": "after-used" }` option:
+
+```js
+/*eslint no-unused-vars: ["error", { "args": "after-used" }]*/
+
+// 2 errors, for the parameters after the last used parameter (bar)
+// "baz" is defined but never used
+// "qux" is defined but never used
+(function(foo, bar, baz, qux) {
+  return bar;
+})();
+```
+
+Examples of **correct** code for the default `{ "args": "after-used" }` option:
+
+```js
+/*eslint no-unused-vars: ["error", {"args": "after-used"}]*/
+
+(function(foo, bar, baz, qux) {
+  return qux;
+})();
+```
+
+#### args: all
+
+Examples of **incorrect** code for the `{ "args": "all" }` option:
+
+```js
+/*eslint no-unused-vars: ["error", { "args": "all" }]*/
+
+// 2 errors
+// "foo" is defined but never used
+// "baz" is defined but never used
+(function(foo, bar, baz) {
+  return bar;
+})();
+```
+
+#### args: none
+
+Examples of **correct** code for the `{ "args": "none" }` option:
+
+```js
+/*eslint no-unused-vars: ["error", { "args": "none" }]*/
+
+(function(foo, bar, baz) {
+  return bar;
+})();
+```
+
+### ignoreRestSiblings
+
+The `ignoreRestSiblings` option is a boolean (default: `false`). Using a [Rest Property](https://github.com/tc39/proposal-object-rest-spread) it is possible to "omit" properties from an object, but by default the sibling properties are marked as "unused". With this option enabled the rest property's siblings are ignored.
+
+Examples of **correct** code for the `{ "ignoreRestSiblings": true }` option:
+
+```js
+/*eslint no-unused-vars: ["error", { "ignoreRestSiblings": true }]*/
+// 'type' is ignored because it has a rest property sibling.
+var { type, ...coords } = data;
+```
+
+### argsIgnorePattern
+
+The `argsIgnorePattern` option specifies exceptions not to check for usage: arguments whose names match a regexp pattern. For example, variables whose names begin with an underscore.
+
+Examples of **correct** code for the `{ "argsIgnorePattern": "^_" }` option:
+
+```js
+/*eslint no-unused-vars: ["error", { "argsIgnorePattern": "^_" }]*/
+
+function foo(x, _y) {
+  return x + 1;
+}
+foo();
+```
+
+### caughtErrors
+
+The `caughtErrors` option is used for `catch` block arguments validation.
+
+It has two settings:
+
+- `none` - do not check error objects. This is the default setting.
+- `all` - all named arguments must be used.
+
+#### caughtErrors: none
+
+Not specifying this rule is equivalent of assigning it to `none`.
+
+Examples of **correct** code for the `{ "caughtErrors": "none" }` option:
+
+```js
+/*eslint no-unused-vars: ["error", { "caughtErrors": "none" }]*/
+
+try {
+  //...
+} catch (err) {
+  console.error('errors');
+}
+```
+
+#### caughtErrors: all
+
+Examples of **incorrect** code for the `{ "caughtErrors": "all" }` option:
+
+```js
+/*eslint no-unused-vars: ["error", { "caughtErrors": "all" }]*/
+
+// 1 error
+// "err" is defined but never used
+try {
+  //...
+} catch (err) {
+  console.error('errors');
+}
+```
+
+### caughtErrorsIgnorePattern
+
+The `caughtErrorsIgnorePattern` option specifies exceptions not to check for usage: catch arguments whose names match a regexp pattern. For example, variables whose names begin with a string 'ignore'.
+
+Examples of **correct** code for the `{ "caughtErrorsIgnorePattern": "^ignore" }` option:
+
+```js
+/*eslint no-unused-vars: ["error", { "caughtErrorsIgnorePattern": "^ignore" }]*/
+
+try {
+  //...
+} catch (ignoreErr) {
+  console.error('errors');
+}
+```
+
+## When Not To Use It
+
+If you don't want to be notified about unused variables or function arguments, you can safely turn this rule off.
+
+<sup>Taken with ❤️ [from ESLint core](https://github.com/eslint/eslint/blob/master/docs/rules/no-unused-vars.md)</sup>

package/packages/less/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-use-before-define.md

@@ -0,0 +1,171 @@
+# Disallow the use of variables before they are defined (no-use-before-define)
+
+In JavaScript, prior to ES6, variable and function declarations are hoisted to the top of a scope, so it's possible to use identifiers before their formal declarations in code. This can be confusing and some believe it is best to always declare variables and functions before using them.
+
+In ES6, block-level bindings (`let` and `const`) introduce a "temporal dead zone" where a `ReferenceError` will be thrown with any attempt to access the variable before its declaration.
+
+## Rule Details
+
+This rule will warn when it encounters a reference to an identifier that has not yet been declared.
+
+Examples of **incorrect** code for this rule:
+
+```ts
+/*eslint no-use-before-define: "error"*/
+/*eslint-env es6*/
+
+alert(a);
+var a = 10;
+
+f();
+function f() {}
+
+function g() {
+  return b;
+}
+var b = 1;
+
+// With blockBindings: true
+{
+  alert(c);
+  let c = 1;
+}
+
+let myVar: StringOrNumber;
+type StringOrNumber = string | number;
+```
+
+Examples of **correct** code for this rule:
+
+```ts
+/*eslint no-use-before-define: "error"*/
+/*eslint-env es6*/
+
+var a;
+a = 10;
+alert(a);
+
+function f() {}
+f(1);
+
+var b = 1;
+function g() {
+  return b;
+}
+
+// With blockBindings: true
+{
+  let C;
+  c++;
+}
+
+type StringOrNumber = string | number;
+let myVar: StringOrNumber;
+```
+
+## Options
+
+```json
+{
+  "no-use-before-define": ["error", { "functions": true, "classes": true }]
+}
+```
+
+- `functions` (`boolean`) -
+  The flag which shows whether or not this rule checks function declarations.
+  If this is `true`, this rule warns every reference to a function before the function declaration.
+  Otherwise, ignores those references.
+  Function declarations are hoisted, so it's safe.
+  Default is `true`.
+- `classes` (`boolean`) -
+  The flag which shows whether or not this rule checks class declarations of upper scopes.
+  If this is `true`, this rule warns every reference to a class before the class declaration.
+  Otherwise, ignores those references if the declaration is in upper function scopes.
+  Class declarations are not hoisted, so it might be danger.
+  Default is `true`.
+- `variables` (`boolean`) -
+  This flag determines whether or not the rule checks variable declarations in upper scopes.
+  If this is `true`, the rule warns every reference to a variable before the variable declaration.
+  Otherwise, the rule ignores a reference if the declaration is in an upper scope, while still reporting the reference if it's in the same scope as the declaration.
+  Default is `true`.
+- `typedefs` (`boolean`, **added** in `@typescript-eslint/eslint-plugin`) -
+  The flag which shows whether or not this rule checks type declarations.
+  If this is `true`, this rule warns every reference to a type before the type declaration.
+  Otherwise, ignores those references.
+  Type declarations are hoisted, so it's safe.
+  Default is `true`.
+
+This rule accepts `"nofunc"` string as an option.
+`"nofunc"` is the same as `{ "functions": false, "classes": true }`.
+
+### functions
+
+Examples of **correct** code for the `{ "functions": false }` option:
+
+```js
+/*eslint no-use-before-define: ["error", { "functions": false }]*/
+
+f();
+function f() {}
+```
+
+### classes
+
+Examples of **incorrect** code for the `{ "classes": false }` option:
+
+```js
+/*eslint no-use-before-define: ["error", { "classes": false }]*/
+/*eslint-env es6*/
+
+new A();
+class A {}
+```
+
+Examples of **correct** code for the `{ "classes": false }` option:
+
+```js
+/*eslint no-use-before-define: ["error", { "classes": false }]*/
+/*eslint-env es6*/
+
+function foo() {
+  return new A();
+}
+
+class A {}
+```
+
+### variables
+
+Examples of **incorrect** code for the `{ "variables": false }` option:
+
+```js
+/*eslint no-use-before-define: ["error", { "variables": false }]*/
+
+console.log(foo);
+var foo = 1;
+```
+
+Examples of **correct** code for the `{ "variables": false }` option:
+
+```js
+/*eslint no-use-before-define: ["error", { "variables": false }]*/
+
+function baz() {
+  console.log(foo);
+}
+
+var foo = 1;
+```
+
+### typedefs
+
+Examples of **correct** code for the `{ "typedefs": false }` option:
+
+```ts
+/*eslint no-use-before-define: ["error", { "typedefs": false }]*/
+
+let myVar: StringOrNumber;
+type StringOrNumber = string | number;
+```
+
+Copied from [the original ESLint rule docs](https://github.com/eslint/eslint/blob/a113cd3/docs/rules/no-use-before-define.md)

package/packages/less/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-useless-constructor.md

@@ -0,0 +1,78 @@
+# Disallow unnecessary constructors (no-useless-constructor)
+
+ES2015 provides a default class constructor if one is not specified. As such, it is unnecessary to provide an empty constructor or one that simply delegates into its parent class, as in the following examples:
+
+```js
+class A {
+  constructor() {}
+}
+
+class A extends B {
+  constructor(value) {
+    super(value);
+  }
+}
+```
+
+## Rule Details
+
+This rule flags class constructors that can be safely removed without changing how the class works.
+
+## Examples
+
+Examples of **incorrect** code for this rule:
+
+```js
+/*eslint @typescript-eslint/no-useless-constructor: "error"*/
+
+class A {
+  constructor() {}
+}
+
+class A extends B {
+  constructor(...args) {
+    super(...args);
+  }
+}
+```
+
+Examples of **correct** code for this rule:
+
+```js
+/*eslint @typescript-eslint/no-useless-constructor: "error"*/
+
+class A {}
+
+class A {
+  constructor() {
+    doSomething();
+  }
+}
+
+class A extends B {
+  constructor() {
+    super('foo');
+  }
+}
+
+class A extends B {
+  constructor() {
+    super();
+    doSomething();
+  }
+}
+
+class A extends B {
+  constructor(protected name: string) {}
+}
+
+class A extends B {
+  protected constructor() {}
+}
+```
+
+## When Not To Use It
+
+If you don't want to be notified about unnecessary constructors, you can safely disable this rule.
+
+<sup>Taken with ❤️ [from ESLint core](https://github.com/eslint/eslint/blob/master/docs/rules/no-useless-constructor.md)</sup>

package/packages/less/node_modules/@typescript-eslint/eslint-plugin/docs/rules/no-var-requires.md

@@ -0,0 +1,28 @@
+# Disallows the use of require statements except in import statements (no-var-requires)
+
+In other words, the use of forms such as `var foo = require("foo")` are banned. Instead use ES6 style imports or `import foo = require("foo")` imports.
+
+## Rule Details
+
+Examples of **incorrect** code for this rule:
+
+```ts
+var foo = require('foo');
+const foo = require('foo');
+let foo = require('foo');
+```
+
+Examples of **correct** code for this rule:
+
+```ts
+import foo = require('foo');
+require('foo');
+```
+
+## When Not To Use It
+
+If you don't care about TypeScript module syntax, then you will not need this rule.
+
+## Compatibility
+
+- TSLint: [no-var-requires](https://palantir.github.io/tslint/rules/no-var-requires/)

package/packages/less/node_modules/@typescript-eslint/eslint-plugin/docs/rules/prefer-for-of.md

@@ -0,0 +1,41 @@
+# Use for-of loops instead of standard for loops over arrays (prefer-for-of)
+
+This rule recommends a for-of loop when the loop index is only used to read from an array that is being iterated.
+
+## Rule Details
+
+For cases where the index is only used to read from the array being iterated, a for-of loop is easier to read and write.
+
+Examples of **incorrect** code for this rule:
+
+```js
+for (let i = 0; i < arr.length; i++) {
+  console.log(arr[i]);
+}
+```
+
+Examples of **correct** code for this rule:
+
+```js
+for (const x of arr) {
+  console.log(x);
+}
+
+for (let i = 0; i < arr.length; i++) {
+  // i is used to write to arr, so for-of could not be used.
+  arr[i] = 0;
+}
+
+for (let i = 0; i < arr.length; i++) {
+  // i is used independent of arr, so for-of could not be used.
+  console.log(i, arr[i]);
+}
+```
+
+## When Not To Use It
+
+If you transpile for browsers that do not support for-of loops, you may wish to use traditional for loops that produce more compact code.
+
+## Related to
+
+- TSLint: ['prefer-for-of'](https://palantir.github.io/tslint/rules/prefer-for-of/)