xo 0.49.0 → 0.52.0

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/space-before-blocks.md

@@ -1,11 +1,17 @@
-# `space-before-blocks`
+---
+description: 'Enforce consistent spacing before blocks.'
+---
 
-Enforces consistent spacing before blocks.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/space-before-blocks** for documentation.
 
 ## Rule Details
 
 This rule extends the base [`eslint/space-before-blocks`](https://eslint.org/docs/rules/space-before-blocks) rule.
-It adds support for interfaces and enums:
+It adds support for interfaces and enums.
+
+<!-- tabs -->
 
 ### ❌ Incorrect
 
@@ -31,32 +37,6 @@ interface State {
 }
 ```
 
-In case a more specific options object is passed these blocks will follow `classes` configuration option.
-
-## How to Use
-
-```jsonc
-{
-  // note you must disable the base rule as it can report incorrect errors
-  "space-before-blocks": "off",
-  "@typescript-eslint/space-before-blocks": ["error"]
-}
-```
-
 ## Options
 
-See [`eslint/space-before-blocks` options](https://eslint.org/docs/rules/space-before-blocks#options).
-
-<sup>
-
-Taken with ❤️ [from ESLint core](https://github.com/eslint/eslint/blob/master/docs/rules/space-before-blocks.md)
-
-</sup>
-
-## Attributes
-
-- Configs:
-  - [ ] ✅ Recommended
-  - [ ] 🔒 Strict
-- [x] 🔧 Fixable
-- [ ] 💭 Requires type information
+In case a more specific options object is passed these blocks will follow `classes` configuration option.

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/space-before-function-paren.md

@@ -1,36 +1,12 @@
-# `space-before-function-paren`
+---
+description: 'Enforce consistent spacing before function parenthesis.'
+---
 
-Enforces consistent spacing before function parenthesis.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/space-before-function-paren** for documentation.
 
 ## Rule Details
 
 This rule extends the base [`eslint/space-before-function-paren`](https://eslint.org/docs/rules/space-before-function-paren) rule.
 It adds support for generic type parameters on function calls.
-
-## How to Use
-
-```jsonc
-{
-  // note you must disable the base rule as it can report incorrect errors
-  "space-before-function-paren": "off",
-  "@typescript-eslint/space-before-function-paren": ["error"]
-}
-```
-
-## Options
-
-See [`eslint/space-before-function-paren` options](https://eslint.org/docs/rules/space-before-function-paren#options).
-
-<sup>
-
-Taken with ❤️ [from ESLint core](https://github.com/eslint/eslint/blob/main/docs/rules/space-before-function-paren.md)
-
-</sup>
-
-## Attributes
-
-- Configs:
-  - [ ] ✅ Recommended
-  - [ ] 🔒 Strict
-- [x] 🔧 Fixable
-- [ ] 💭 Requires type information

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/space-infix-ops.md

@@ -1,40 +1,16 @@
-# `space-infix-ops`
+---
+description: 'Require spacing around infix operators.'
+---
 
-This rule is aimed at ensuring there are spaces around infix operators..
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/space-infix-ops** for documentation.
 
 This rule extends the base [`eslint/space-infix-ops`](https://eslint.org/docs/rules/space-infix-ops) rule.
-
-It also add support for enum members
+It adds support for enum members.
 
 ```ts
 enum MyEnum {
   KEY = 'value',
 }
 ```
-
-## How to Use
-
-```jsonc
-{
-  "space-infix-ops": "off",
-  "@typescript-eslint/space-infix-ops": ["error", { "int32Hint": false }]
-}
-```
-
-## Options
-
-See [`eslint/space-infix-ops` options](https://eslint.org/docs/rules/space-infix-ops#options).
-
-<sup>
-
-Taken with ❤️ [from ESLint core](https://github.com/eslint/eslint/blob/main/docs/rules/space-infix-ops.md)
-
-</sup>
-
-## Attributes
-
-- Configs:
-  - [ ] ✅ Recommended
-  - [ ] 🔒 Strict
-- [x] 🔧 Fixable
-- [ ] 💭 Requires type information

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/strict-boolean-expressions.md

@@ -1,6 +1,10 @@
-# `strict-boolean-expressions`
+---
+description: 'Disallow certain types in boolean expressions.'
+---
 
-Restricts the types allowed in boolean expressions.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/strict-boolean-expressions** for documentation.
 
 Forbids usage of non-boolean types in expressions where a boolean is expected.
 `boolean` and `never` types are always allowed.
@@ -85,29 +89,6 @@ const foo = (arg: any) => (Boolean(arg) ? 1 : 0);
 
 ## Options
 
-```ts
-type Options = {
-  allowString?: boolean;
-  allowNumber?: boolean;
-  allowNullableObject?: boolean;
-  allowNullableBoolean?: boolean;
-  allowNullableString?: boolean;
-  allowNullableNumber?: boolean;
-  allowAny?: boolean;
-};
-
-const defaultOptions: Options = {
-  allowString: true,
-  allowNumber: true,
-  allowNullableObject: true,
-  allowNullableBoolean: false,
-  allowNullableString: false,
-  allowNullableNumber: false,
-  allowAny: false,
-  allowRuleToRunWithoutStrictNullChecksIKnowWhatIAmDoing: false,
-};
-```
-
 ### `allowString`
 
 Allows `string` in a boolean context.
@@ -195,13 +176,4 @@ This rule provides following fixes and suggestions for particular types in boole
 
 ## Related To
 
-- TSLint: [strict-boolean-expressions](https://palantir.github.io/tslint/rules/strict-boolean-expressions)
 - [no-unnecessary-condition](./no-unnecessary-condition.md) - Similar rule which reports always-truthy and always-falsy values in conditions
-
-## Attributes
-
-- Configs:
-  - [ ] ✅ Recommended
-  - [ ] 🔒 Strict
-- [x] 🔧 Fixable
-- [x] 💭 Requires type information

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/switch-exhaustiveness-check.md

@@ -1,6 +1,10 @@
-# `switch-exhaustiveness-check`
+---
+description: 'Require switch-case statements to be exhaustive with union type.'
+---
 
-Exhaustiveness checking in switch with union type.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/switch-exhaustiveness-check** for documentation.
 
 Union type may have a lot of parts. It's easy to forget to consider all cases in switch. This rule reminds which parts are missing. If domain of the problem requires to have only a partial switch, developer may _explicitly_ add a default clause.
 
@@ -106,27 +110,6 @@ switch (day) {
 }
 ```
 
-## Options
-
-```jsonc
-// .eslintrc.json
-{
-  "rules": {
-    "@typescript-eslint/switch-exhaustiveness-check": "warn"
-  }
-}
-```
-
-This rule is not configurable.
-
 ## When Not To Use It
 
 If program doesn't have union types with many parts. Downside of this rule is the need for type information, so it's slower than regular rules.
-
-## Attributes
-
-- Configs:
-  - [ ] ✅ Recommended
-  - [ ] 🔒 Strict
-- [ ] 🔧 Fixable
-- [x] 💭 Requires type information

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/triple-slash-reference.md

@@ -1,10 +1,16 @@
-# `triple-slash-reference`
+---
+description: 'Disallow certain triple slash directives in favor of ES6-style import declarations.'
+---
 
-Sets preference level for triple slash directives versus ES6-style import declarations.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/triple-slash-reference** for documentation.
+
+## Rule Details
 
 Use of triple-slash reference type directives is discouraged in favor of the newer `import` style. This rule allows you to ban use of `/// <reference path="" />`, `/// <reference types="" />`, or `/// <reference lib="" />` directives.
 
-## Rule Details
+## Options
 
 With `{ "path": "never", "types": "never", "lib": "never" }` options set, the following will all be **incorrect** usage:
 
@@ -51,16 +57,3 @@ If you want to ban use of one or all of the triple slash reference directives, o
 ## When Not To Use It
 
 If you want to use all flavors of triple slash reference directives.
-
-## Related To
-
-- TSLint: [no-reference](http://palantir.github.io/tslint/rules/no-reference/)
-- TSLint: [no-reference-import](https://palantir.github.io/tslint/rules/no-reference-import/)
-
-## Attributes
-
-- Configs:
-  - [x] ✅ Recommended
-  - [x] 🔒 Strict
-- [ ] 🔧 Fixable
-- [ ] 💭 Requires type information

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/type-annotation-spacing.md

@@ -1,6 +1,10 @@
-# `type-annotation-spacing`
+---
+description: 'Require consistent spacing around type annotations.'
+---
 
-Require consistent spacing around type annotations.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/type-annotation-spacing** for documentation.
 
 Spacing around type annotations improves readability of the code. Although the most commonly used style guideline for type annotations in TypeScript prescribes adding a space after the colon, but not before it, it is subjective to the preferences of a project. For example:
 
@@ -37,21 +41,11 @@ This rule aims to enforce specific spacing patterns around type annotations and
 
 ## Options
 
-This rule has an object option:
-
-- `"before": false`, (default for colon) disallows spaces before the colon/arrow.
-- `"before": true`, (default for arrow) requires a space before the colon/arrow.
-- `"after": true`, (default) requires a space after the colon/arrow.
-- `"after": false`, disallows spaces after the colon/arrow.
-- `"overrides"`, overrides the default options for type annotations with `colon` (e.g. `const foo: string`) and function types with `arrow` (e.g. `type Foo = () => {}`). Additionally allows granular overrides for `variable` (`const foo: string`),`parameter` (`function foo(bar: string) {...}`),`property` (`interface Foo { bar: string }`) and `returnType` (`function foo(): string {...}`) annotations.
-
-### defaults
-
 Examples of code for this rule with no options at all:
 
 <!--tabs-->
 
-#### ❌ Incorrect
+### ❌ Incorrect
 
 <!-- prettier-ignore -->
 ```ts
@@ -80,7 +74,7 @@ type Foo = () =>{};
 type Foo = ()=> {};
 ```
 
-#### ✅ Correct
+### ✅ Correct
 
 <!-- prettier-ignore -->
 ```ts
@@ -307,15 +301,3 @@ If you don't want to enforce spacing for your type annotations, you can safely t
 
 - [TypeScript Type System](https://basarat.gitbooks.io/typescript/docs/types/type-system.html)
 - [Type Inference](https://www.typescriptlang.org/docs/handbook/type-inference.html)
-
-## Related To
-
-- TSLint: [`typedef-whitespace`](https://palantir.github.io/tslint/rules/typedef-whitespace/)
-
-## Attributes
-
-- Configs:
-  - [ ] ✅ Recommended
-  - [ ] 🔒 Strict
-- [x] 🔧 Fixable
-- [ ] 💭 Requires type information

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/typedef.md

@@ -1,6 +1,10 @@
-# `typedef`
+---
+description: 'Require type annotations in certain places.'
+---
 
-Requires type annotations to exist.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/typedef** for documentation.
 
 TypeScript cannot always infer types for all places in code.
 Some locations require type annotations for their types to be inferred.
@@ -18,44 +22,24 @@ class ContainsText {
 }
 ```
 
-**_Note:_** requiring type annotations unnecessarily can be cumbersome to maintain and generally reduces code readability.
+:::caution
+
+Requiring type annotations unnecessarily can be cumbersome to maintain and generally reduces code readability.
 TypeScript is often better at inferring types than easily written type annotations would allow.
 
 **Instead of enabling `typedef`, it is generally recommended to use the `--noImplicitAny` and `--strictPropertyInitialization` compiler options to enforce type annotations only when useful.**
 
+:::
+
 ## Rule Details
 
 This rule can enforce type annotations in locations regardless of whether they're required.
 This is typically used to maintain consistency for element types that sometimes require them.
 
-> To enforce type definitions existing on call signatures as per TSLint's `arrow-call-signature` and `call-signature` options, use `explicit-function-return-type`, or `explicit-module-boundary-types`.
+> To enforce type definitions existing on call signatures, use `explicit-function-return-type`, or `explicit-module-boundary-types`.
 
 ## Options
 
-```ts
-type Options = {
-  arrayDestructuring?: boolean;
-  arrowParameter?: boolean;
-  memberVariableDeclaration?: boolean;
-  objectDestructuring?: boolean;
-  parameter?: boolean;
-  propertyDeclaration?: boolean;
-  variableDeclaration?: boolean;
-  variableDeclarationIgnoreFunction?: boolean;
-};
-
-const defaultOptions: Options = {
-  arrayDestructuring: false,
-  arrowParameter: false,
-  memberVariableDeclaration: false,
-  objectDestructuring: false,
-  parameter: false,
-  propertyDeclaration: false,
-  variableDeclaration: false,
-  variableDeclarationIgnoreFunction: false,
-};
-```
-
 For example, with the following configuration:
 
 ```json
@@ -336,15 +320,3 @@ In general, if you do not consider the cost of writing unnecessary type annotati
 
 - [TypeScript Type System](https://basarat.gitbooks.io/typescript/docs/types/type-system.html)
 - [Type Inference](https://www.typescriptlang.org/docs/handbook/type-inference.html)
-
-## Related To
-
-- TSLint: [`typedef`](https://palantir.github.io/tslint/rules/typedef)
-
-## Attributes
-
-- Configs:
-  - [ ] ✅ Recommended
-  - [ ] 🔒 Strict
-- [ ] 🔧 Fixable
-- [ ] 💭 Requires type information

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/unbound-method.md

@@ -1,18 +1,19 @@
-# `unbound-method`
+---
+description: 'Enforce unbound methods are called with their expected scope.'
+---
 
-Enforces unbound methods are called with their expected scope.
-
-Warns when a method is used outside of a method call.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/unbound-method** for documentation.
 
 Class functions don't preserve the class scope when passed as standalone variables.
-
 If your function does not access `this`, [you can annotate it with `this: void`](https://www.typescriptlang.org/docs/handbook/2/functions.html#declaring-this-in-a-function), or consider using an arrow function instead.
 
 If you're working with `jest`, you can use [`eslint-plugin-jest`'s version of this rule](https://github.com/jest-community/eslint-plugin-jest/blob/main/docs/rules/unbound-method.md) to lint your test files, which knows when it's ok to pass an unbound method to `expect` calls.
 
 ## Rule Details
 
-Examples of code for this rule
+Examples of code for this rule with the default options:
 
 <!--tabs-->
 
@@ -75,10 +76,6 @@ const { double } = arith;
 
 ## Options
 
-The rule accepts an options object with the following property:
-
-- `ignoreStatic` to not check whether `static` methods are correctly bound
-
 ### `ignoreStatic`
 
 Examples of **correct** code for this rule with `{ ignoreStatic: true }`:
@@ -96,33 +93,8 @@ const { log } = OtherClass;
 log();
 ```
 
-## Example
-
-```json
-{
-  "@typescript-eslint/unbound-method": [
-    "error",
-    {
-      "ignoreStatic": true
-    }
-  ]
-}
-```
-
 ## When Not To Use It
 
 If your code intentionally waits to bind methods after use, such as by passing a `scope: this` along with the method, you can disable this rule.
 
 If you're wanting to use `toBeCalled` and similar matches in `jest` tests, you can disable this rule for your test files in favor of [`eslint-plugin-jest`'s version of this rule](https://github.com/jest-community/eslint-plugin-jest/blob/main/docs/rules/unbound-method.md).
-
-## Related To
-
-- TSLint: [no-unbound-method](https://palantir.github.io/tslint/rules/no-unbound-method/)
-
-## Attributes
-
-- Configs:
-  - [x] ✅ Recommended
-  - [x] 🔒 Strict
-- [ ] 🔧 Fixable
-- [x] 💭 Requires type information

package/node_modules/@typescript-eslint/eslint-plugin/docs/rules/unified-signatures.md

@@ -1,27 +1,15 @@
-# `unified-signatures`
+---
+description: 'Disallow two overloads that could be unified into one with a union or an optional/rest parameter.'
+---
 
-Warns for any two overloads that could be unified into one by using a union or an optional/rest parameter.
+> 🛑 This file is source code, not the primary documentation location! 🛑
+>
+> See **https://typescript-eslint.io/rules/unified-signatures** for documentation.
 
 ## Rule Details
 
 This rule aims to keep the source code as maintainable as possible by reducing the amount of overloads.
 
-## Options
-
-```ts
-type Options = {
-  ignoreDifferentlyNamedParameters?: boolean;
-};
-
-const defaultOptions: Options = {
-  ignoreDifferentlyNamedParameters: false,
-};
-```
-
-The rule accepts an options object with the following property:
-
-- `ignoreDifferentlyNamedParameters`: whether two parameters with different names at the same index should be considered different even if their types are the same.
-
 Examples of code for this rule with the default options:
 
 <!--tabs-->
@@ -48,6 +36,10 @@ function x(x: number | string): void;
 function y(...x: number[]): void;
 ```
 
+## Options
+
+### `ignoreDifferentlyNamedParameters`
+
 Examples of code for this rule with `ignoreDifferentlyNamedParameters`:
 
 <!--tabs-->
@@ -76,14 +68,4 @@ function f(...a: number[]): void;
 function f(...a: string[]): void;
 ```
 
-## Related To
-
-- TSLint: [`unified-signatures`](https://palantir.github.io/tslint/rules/unified-signatures/)
-
-## Attributes
-
-- Configs:
-  - [ ] ✅ Recommended
-  - [x] 🔒 Strict
-- [ ] 🔧 Fixable
-- [ ] 💭 Requires type information
+## Options

package/node_modules/@typescript-eslint/eslint-plugin/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@typescript-eslint/eslint-plugin",
-  "version": "5.24.0",
+  "version": "5.35.1",
   "description": "TypeScript plugin for ESLint",
   "keywords": [
     "eslint",
@@ -36,17 +36,17 @@
     "check-configs": "jest tests/configs.test.ts --runTestsByPath --silent --runInBand",
     "clean": "tsc -b tsconfig.build.json --clean",
     "postclean": "rimraf dist && rimraf coverage",
-    "format": "prettier --write \"./**/*.{ts,js,json,md}\" --ignore-path ../../.prettierignore",
+    "format": "prettier --write \"./**/*.{ts,mts,cts,tsx,js,mjs,cjs,jsx,json,md,css}\" --ignore-path ../../.prettierignore",
     "generate:configs": "../../node_modules/.bin/ts-node --files --transpile-only tools/generate-configs.ts",
     "generate:rules-lists": "../../node_modules/.bin/ts-node --files --transpile-only tools/generate-rules-lists.ts",
-    "lint": "eslint . --ext .js,.ts --ignore-path ../../.eslintignore",
+    "lint": "eslint . --ignore-path ../../.eslintignore",
     "test": "jest --coverage",
     "typecheck": "tsc -p tsconfig.json --noEmit"
   },
   "dependencies": {
-    "@typescript-eslint/scope-manager": "5.24.0",
-    "@typescript-eslint/type-utils": "5.24.0",
-    "@typescript-eslint/utils": "5.24.0",
+    "@typescript-eslint/scope-manager": "5.35.1",
+    "@typescript-eslint/type-utils": "5.35.1",
+    "@typescript-eslint/utils": "5.35.1",
     "debug": "^4.3.4",
     "functional-red-black-tree": "^1.0.1",
     "ignore": "^5.2.0",
@@ -79,5 +79,5 @@
     "type": "opencollective",
     "url": "https://opencollective.com/typescript-eslint"
   },
-  "gitHead": "2f57f3f398412e108e2ef86df71f076207c8e81b"
+  "gitHead": "cb43b4a19dcb967c3342dc8e677e57097b76d888"
 }

package/node_modules/@typescript-eslint/parser/README.md

@@ -78,16 +78,19 @@ 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:
+**NOTE:** this setting does not affect known file types (`.js`, `.mjs`, `.cjs`, `.jsx`, `.ts`, `.mts`, `.cts`, `.tsx`, `.json`) because the TypeScript compiler has its own internal handling for known file extensions.
 
-- 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**.
+<!-- https://github.com/microsoft/TypeScript/blob/d6e483b8dabd8fd37c00954c3f2184bb7f1eb90c/src/compiler/utilities.ts#L6281-L6285 -->
+
+The exact behavior is as follows:
+
+- `.js`, `.mjs`, `.cjs`, `.jsx`, `.tsx` files are always parsed as if this is `true`.
+- `.ts`, `.mts`, `.cts` files are always parsed as if this is `false`.
+- For "unknown" extensions (`.md`, `.vue`):
+  - If `parserOptions.project` is _not_ provided:
+    - The setting will be respected.
+  - If `parserOptions.project` is provided (i.e. you are using rules with type information):
+    - **always parsed as if this is `false`**
 
 ### `parserOptions.ecmaFeatures.globalReturn`
 
@@ -203,7 +206,8 @@ For example, by default it will ensure that a glob like `./**/tsconfig.json` wil
 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"]`.
+The default extensions are `['.js', '.mjs', '.cjs', '.jsx', '.ts', '.mts', '.cts', '.tsx']`.
+Add extensions starting with `.`, followed by the file extension. E.g. for a `.vue` file use `"extraFileExtensions": [".vue"]`.
 
 ### `parserOptions.warnOnUnsupportedTypeScriptVersion`
 
@@ -252,7 +256,7 @@ Note that if you pass custom programs via `options.programs` this option will no
 
 Default `undefined`.
 
-This option allow you to tell parser to act as if `emitDecoratorMetadata: true` is set in `tsconfig.json`, but without [type-aware linting](https://typescript-eslint.io/docs/linting/type-linting). In other words, you don't have to specify `parserOptions.project` in this case, making the linting process faster.
+This option allow you to tell parser to act as if `emitDecoratorMetadata: true` is set in `tsconfig.json`, but without [type-aware linting](https://typescript-eslint.io/docs/linting/typed-linting). In other words, you don't have to specify `parserOptions.project` in this case, making the linting process faster.
 
 ## Utilities
 

package/node_modules/@typescript-eslint/parser/dist/parser.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"parser.d.ts","sourceRoot":"","sources":["../src/parser.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,aAAa,EAAE,QAAQ,EAAO,MAAM,0BAA0B,CAAC;AACxE,OAAO,EAEL,cAAc,EAEd,WAAW,EACZ,MAAM,sCAAsC,CAAC;AAC9C,OAAO,EAGL,YAAY,EACb,MAAM,kCAAkC,CAAC;AAM1C,UAAU,oBAAoB;IAC5B,GAAG,EAAE,QAAQ,CAAC,OAAO,GAAG;QACtB,KAAK,CAAC,EAAE,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;QACzB,MAAM,CAAC,EAAE,QAAQ,CAAC,KAAK,EAAE,CAAC;QAC1B,QAAQ,CAAC,EAAE,QAAQ,CAAC,OAAO,EAAE,CAAC;KAC/B,CAAC;IACF,QAAQ,EAAE,cAAc,CAAC;IACzB,WAAW,EAAE,OAAO,WAAW,CAAC;IAChC,YAAY,EAAE,YAAY,CAAC;CAC5B;AA+CD,iBAAS,KAAK,CACZ,IAAI,EAAE,MAAM,EACZ,OAAO,CAAC,EAAE,aAAa,GACtB,oBAAoB,CAAC,KAAK,CAAC,CAE7B;AAED,iBAAS,cAAc,CACrB,IAAI,EAAE,MAAM,EACZ,OAAO,CAAC,EAAE,aAAa,GAAG,IAAI,GAC7B,oBAAoB,CAgGtB;AAED,OAAO,EAAE,KAAK,EAAE,cAAc,EAAE,aAAa,EAAE,CAAC"}
+{"version":3,"file":"parser.d.ts","sourceRoot":"","sources":["../src/parser.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,aAAa,EAAE,QAAQ,EAAO,MAAM,0BAA0B,CAAC;AACxE,OAAO,EAEL,cAAc,EAEd,WAAW,EACZ,MAAM,sCAAsC,CAAC;AAC9C,OAAO,EAGL,YAAY,EACb,MAAM,kCAAkC,CAAC;AAM1C,UAAU,oBAAoB;IAC5B,GAAG,EAAE,QAAQ,CAAC,OAAO,GAAG;QACtB,KAAK,CAAC,EAAE,CAAC,MAAM,EAAE,MAAM,CAAC,CAAC;QACzB,MAAM,CAAC,EAAE,QAAQ,CAAC,KAAK,EAAE,CAAC;QAC1B,QAAQ,CAAC,EAAE,QAAQ,CAAC,OAAO,EAAE,CAAC;KAC/B,CAAC;IACF,QAAQ,EAAE,cAAc,CAAC;IACzB,WAAW,EAAE,OAAO,WAAW,CAAC;IAChC,YAAY,EAAE,YAAY,CAAC;CAC5B;AA+CD,iBAAS,KAAK,CACZ,IAAI,EAAE,MAAM,EACZ,OAAO,CAAC,EAAE,aAAa,GACtB,oBAAoB,CAAC,KAAK,CAAC,CAE7B;AAED,iBAAS,cAAc,CACrB,IAAI,EAAE,MAAM,EACZ,OAAO,CAAC,EAAE,aAAa,GAAG,IAAI,GAC7B,oBAAoB,CAwFtB;AAED,OAAO,EAAE,KAAK,EAAE,cAAc,EAAE,aAAa,EAAE,CAAC"}