kibana/packages/kbn-eslint-plugin-eslint/package.json

{
  "name": "@kbn/eslint-plugin-eslint",
  "version": "1.0.0",
  "private": true,
  "license": "Apache-2.0",
  "peerDependencies": {
    "eslint": "6.8.0",
    "babel-eslint": "^10.0.3"
  },
  "dependencies": {
    "micromatch": "3.1.10",
    "dedent": "^0.7.0",
    "eslint-module-utils": "2.5.0"
  }
}
Migrate x-pack-kibana source to kibana 2018-04-20 21:13:37 +02:00			`{`
[eslint] merge custom rules into a single plugin (#33733) I'd like to add another custom eslint rule, but there isn't a very good place to do that right now. We have the `eslint-plugin-kibana-custom` package, which is super simple but isn't in the `@kbn` namespace and isn't included in the root eslint config, and `@kbn/eslint-plugin-license-header` is too specific, so I've merged those two packages into `@kbn/eslint-plugin-eslint`, which is a little redundant but allows is to refer to the rules within it as `@kbn/eslint/{rule}`, which feels nice. Thoughts? _NOTE:_ merging the eslint rules from the two packages means enabling prettier for the code from `@kbn/eslint-plugin-license-header`, all those changes are made in https://github.com/elastic/kibana/pull/33733/commits/42c7da6fe2631f513637ab07058be3f833ee7adb. [View the changes without the prettier updates](https://github.com/elastic/kibana/compare/b647f2b...74e07a0) 2019-03-23 01:12:14 +01:00			`"name": "@kbn/eslint-plugin-eslint",`
Migrate x-pack-kibana source to kibana 2018-04-20 21:13:37 +02:00			`"version": "1.0.0",`
			`"private": true,`
			`"license": "Apache-2.0",`
			`"peerDependencies": {`
Update eslint related packages (#54107) 2020-01-07 19:08:36 +01:00			`"eslint": "6.8.0",`
Update dependency babel-eslint to ^10.0.3 (#44029) 2019-08-27 22:57:15 +02:00			`"babel-eslint": "^10.0.3"`
Migrate x-pack-kibana source to kibana 2018-04-20 21:13:37 +02:00			`},`
			`"dependencies": {`
[New platform] Restrict import from core&plugin internals for js files (#33697) * restrict import from core&plugin internals * Fork import/no-restricted-paths and add allowSameFolder option Our use case requires to restrict imports from plugin folders, which names are unknown for us yet. We cannot use 'import/no-restricted-paths' in the current state, because if we define 'from: plugins//server/' the rule will report all relative imports in the same folder as well. To fix this problem we added another option 'allowSameFolder' that makes the rule to ignore imports in the same folder. update notices * add basePath option * support glob pattern instead of reagexp * remove @notice, make basePath required 2019-03-29 08:48:32 +01:00			`"micromatch": "3.1.10",`
			`"dedent": "^0.7.0",`
Update eslint related packages (#54107) 2020-01-07 19:08:36 +01:00			`"eslint-module-utils": "2.5.0"`
Migrate x-pack-kibana source to kibana 2018-04-20 21:13:37 +02:00			`}`
			`}`