immosquare-cleaner 0.1.34 → 0.1.35

data/node_modules/eslint-plugin-import/docs/rules/prefer-default-export.md

@@ -1,185 +0,0 @@
-# import/prefer-default-export
-
-<!-- end auto-generated rule header -->
-
-In exporting files, this rule checks if there is default export or not.
-
-## Rule Details
-
-### rule schema
-
-```javascript
-"import/prefer-default-export": [
-    ( "off" | "warn" | "error" ),
-    { "target": "single" | "any" } // default is "single"
-]
-```
-
-### Config Options
-
-There are two options available: `single` and `any`. By default, if you do not specify the option, rule will assume it is `single`.
-
-#### single
-
-**Definition**: When there is only a single export from a module, prefer using default export over named export.
-
-How to setup config file for this rule:
-
-```javascript
-// you can manually specify it
-"rules": {
-    "import/prefer-default-export": [
-        ( "off" | "warn" | "error" ),
-        { "target": "single" }
-    ]
-}
-
-// config setup below will also work
-"rules": {
-    "import/prefer-default-export": "off" | "warn" | "error"
-}
-```
-
-The following patterns are considered warnings:
-
-```javascript
-// bad.js
-
-// There is only a single module export and it's a named export.
-export const foo = 'foo';
-
-```
-
-The following patterns are not warnings:
-
-```javascript
-// good1.js
-
-// There is a default export.
-export const foo = 'foo';
-const bar = 'bar';
-export default bar;
-```
-
-```javascript
-// good2.js
-
-// There is more than one named export in the module.
-export const foo = 'foo';
-export const bar = 'bar';
-```
-
-```javascript
-// good3.js
-
-// There is more than one named export in the module
-const foo = 'foo';
-const bar = 'bar';
-export { foo, bar }
-```
-
-```javascript
-// good4.js
-
-// There is a default export.
-const foo = 'foo';
-export { foo as default }
-```
-
-```javascript
-// export-star.js
-
-// Any batch export will disable this rule. The remote module is not inspected.
-export * from './other-module'
-```
-
-#### any
-
-**Definition**: any exporting file must contain a default export.
-
-How to setup config file for this rule:
-
-```javascript
-// you have to manually specify it
-"rules": {
-    "import/prefer-default-export": [
-        ( "off" | "warn" | "error" ),
-        { "target": "any" }
-    ]
-}
-```
-
-The following patterns are *not* considered warnings:
-
-```javascript
-// good1.js
-
-//has default export
-export default function bar() {};
-```
-
-```javascript
-// good2.js
-
-// has default export
-let foo;
-export { foo as default }
-```
-
-```javascript
-// good3.js
-
-//contains multiple exports AND default export
-export const a = 5;
-export function bar(){};
-let foo;
-export { foo as default }
-```
-
-```javascript
-// good4.js
-
-// does not contain any exports => file is not checked by the rule
-import * as foo from './foo';
-```
-
-```javascript
-// export-star.js
-
-// Any batch export will disable this rule. The remote module is not inspected.
-export * from './other-module'
-```
-
-The following patterns are considered warnings:
-
-```javascript
-// bad1.js
-
-//has 2 named exports, but no default export
-export const foo = 'foo';
-export const bar = 'bar';
-```
-
-```javascript
-// bad2.js
-
-// does not have default export
-let foo, bar;
-export { foo, bar }
-```
-
-```javascript
-// bad3.js
-
-// does not have default export
-export { a, b } from "foo.js"
-```
-
-```javascript
-// bad4.js
-
-// does not have default export
-let item;
-export const foo = item;
-export { item };
-```

data/node_modules/eslint-plugin-import/docs/rules/unambiguous.md

@@ -1,57 +0,0 @@
-# import/unambiguous
-
-<!-- end auto-generated rule header -->
-
-Warn if a `module` could be mistakenly parsed as a `script` by a consumer leveraging
-[Unambiguous JavaScript Grammar] to determine correct parsing goal.
-
-Will respect the [`parserOptions.sourceType`] from ESLint config, i.e. files parsed
-as `script` per that setting will not be reported.
-
-This plugin uses [Unambiguous JavaScript Grammar] internally to decide whether
-dependencies should be parsed as modules and searched for exports matching the
-`import`ed names, so it may be beneficial to keep this rule on even if your application
-will run in an explicit `module`-only environment.
-
-## Rule Details
-
-For files parsed as `module` by ESLint, the following are valid:
-
-```js
-import 'foo'
-function x() { return 42 }
-```
-
-```js
-export function x() { return 42 }
-```
-
-```js
-(function x() { return 42 })()
-export {} // simple way to mark side-effects-only file as 'module' without any imports/exports
-```
-
-...whereas the following file would be reported:
-
-```js
-(function x() { return 42 })()
-```
-
-## When Not To Use It
-
-If your application environment will always know via [some other means](https://github.com/nodejs/node-eps/issues/13)
-how to parse, regardless of syntax, you may not need this rule.
-
-Remember, though, that this plugin uses this strategy internally, so if you were
-to `import` from a module with no `import`s or `export`s, this plugin would not
-report it as it would not be clear whether it should be considered a `script` or
-a `module`.
-
-## Further Reading
-
- - [Unambiguous JavaScript Grammar]
- - [`parserOptions.sourceType`]
- - [node-eps#13](https://github.com/nodejs/node-eps/issues/13)
-
-[`parserOptions.sourceType`]: https://eslint.org/docs/user-guide/configuring#specifying-parser-options
-[Unambiguous JavaScript Grammar]: https://github.com/nodejs/node-eps/blob/HEAD/002-es-modules.md#32-determining-if-source-is-an-es-module