angular-eslint 20.5.3-alpha.2 → 20.5.3-alpha.4

package/dist/index.d.ts

@@ -1,7 +1,17 @@
+import type { Plugin as ESLintPlugin } from '@eslint/core';
 import type { TSESLint } from '@typescript-eslint/utils';
 declare const templateParser: TSESLint.FlatConfig.Parser;
-declare const tsPlugin: TSESLint.FlatConfig.Plugin;
-declare const templatePlugin: TSESLint.FlatConfig.Plugin;
+/**
+ * Make the plugins compatible with both ESLint's Plugin type and typescript-eslint's
+ * FlatConfig.Plugin type through type assertion.
+ *
+ * This is covered by a type compatibility test in tests/type-compatibility.test.ts
+ */
+type CompatiblePlugin = Omit<ESLintPlugin, 'configs'> & {
+    configs?: never;
+};
+declare const tsPlugin: CompatiblePlugin;
+declare const templatePlugin: CompatiblePlugin;
 declare const configs: {
     tsAll: TSESLint.FlatConfig.ConfigArray;
     tsRecommended: TSESLint.FlatConfig.ConfigArray;
@@ -9,7 +19,7 @@ declare const configs: {
     templateRecommended: TSESLint.FlatConfig.ConfigArray;
     templateAccessibility: TSESLint.FlatConfig.ConfigArray;
 };
-declare const processInlineTemplates: TSESLint.Processor.LooseProcessorModule | undefined;
+declare const processInlineTemplates: import("@eslint/core").Processor<string | import("@eslint/core").ProcessorFile> | undefined;
 declare const _default: {
     configs: {
         tsAll: TSESLint.FlatConfig.ConfigArray;
@@ -18,13 +28,13 @@ declare const _default: {
         templateRecommended: TSESLint.FlatConfig.ConfigArray;
         templateAccessibility: TSESLint.FlatConfig.ConfigArray;
     };
-    tsPlugin: TSESLint.FlatConfig.Plugin;
+    tsPlugin: CompatiblePlugin;
     templateParser: {
         meta?: { [K in keyof TSESLint.Parser.ParserMeta]?: TSESLint.Parser.ParserMeta[K] | undefined; };
         parseForESLint(text: string, options?: unknown): { [k in keyof TSESLint.Parser.ParseResult]: unknown; };
     };
-    templatePlugin: TSESLint.FlatConfig.Plugin;
-    processInlineTemplates: TSESLint.Processor.LooseProcessorModule | undefined;
+    templatePlugin: CompatiblePlugin;
+    processInlineTemplates: import("@eslint/core").Processor<string | import("@eslint/core").ProcessorFile> | undefined;
 };
 export default _default;
 export { configs, templateParser, templatePlugin, tsPlugin, processInlineTemplates, };

package/dist/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAGA,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,0BAA0B,CAAC;AASzD,QAAA,MAAM,cAAc,EAAE,QAAQ,CAAC,UAAU,CAAC,MAGzC,CAAC;AAyBF,QAAA,MAAM,QAAQ,EAAE,QAAQ,CAAC,UAAU,CAAC,MAGnC,CAAC;AACF,QAAA,MAAM,cAAc,EAAE,QAAQ,CAAC,UAAU,CAAC,MAGzC,CAAC;AAEF,QAAA,MAAM,OAAO;;;;;;CAYZ,CAAC;AAGF,QAAA,MAAM,sBAAsB,qDACwB,CAAC;;;;;;;;;;;wDA5CA,CAAC;;;;;;AAmDtD,wBAME;AACF,OAAO,EACL,OAAO,EACP,cAAc,EACd,cAAc,EACd,QAAQ,EACR,sBAAsB,GACvB,CAAC"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAGA,OAAO,KAAK,EAAE,MAAM,IAAI,YAAY,EAAE,MAAM,cAAc,CAAC;AAC3D,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,0BAA0B,CAAC;AASzD,QAAA,MAAM,cAAc,EAAE,QAAQ,CAAC,UAAU,CAAC,MAGzC,CAAC;AA4BF;;;;;GAKG;AACH,KAAK,gBAAgB,GAAG,IAAI,CAAC,YAAY,EAAE,SAAS,CAAC,GAAG;IACtD,OAAO,CAAC,EAAE,KAAK,CAAC;CACjB,CAAC;AACF,QAAA,MAAM,QAAQ,EAA8B,gBAAgB,CAAC;AAC7D,QAAA,MAAM,cAAc,EAAoC,gBAAgB,CAAC;AAEzE,QAAA,MAAM,OAAO;;;;;;CAYZ,CAAC;AAGF,QAAA,MAAM,sBAAsB,6FACwB,CAAC;;;;;;;;;;;wDAnDK,CAAA;;;;;;AA0D1D,wBAME;AACF,OAAO,EACL,OAAO,EACP,cAAc,EACd,cAAc,EACd,QAAQ,EACR,sBAAsB,GACvB,CAAC"}

package/dist/index.js

@@ -51,29 +51,6 @@ const templateParser = {
     parseForESLint: templateParserBase.parseForESLint,
 };
 exports.templateParser = templateParser;
-/*
-we could build a plugin object here without the `configs` key - but if we do
-that then we create a situation in which
-```
-require('angular-eslint').tsPlugin !== require('@angular-eslint/eslint-plugin')
-```
-
-This is bad because it means that 3rd party configs would be required to use
-`angular-eslint` or else they would break a user's config if the user either
-used `angular.configs.recommended` et al. or
-```
-{
-  plugins: {
-    '@angular-eslint': angular.tsPlugin,
-  },
-}
-```
-
-This might be something we could consider okay (e.g. 3rd party flat configs must
-use our new package); however legacy configs consumed via `@eslint/eslintrc`
-would never be able to satisfy this constraint and thus users would be blocked
-from using them.
-*/
 const tsPlugin = eslint_plugin_1.default;
 exports.tsPlugin = tsPlugin;
 const templatePlugin = eslint_plugin_template_1.default;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "angular-eslint",
-  "version": "20.5.3-alpha.2",
+  "version": "20.5.3-alpha.4",
   "description": "The tooling which enables ESLint to work with Angular projects",
   "license": "MIT",
   "main": "dist/index.js",
@@ -27,11 +27,11 @@
     "@angular-devkit/schematics": ">= 20.0.0 < 21.0.0",
     "@typescript-eslint/types": "^8.0.0",
     "@typescript-eslint/utils": "^8.0.0",
-    "@angular-eslint/builder": "20.5.3-alpha.2",
-    "@angular-eslint/eslint-plugin-template": "20.5.3-alpha.2",
-    "@angular-eslint/schematics": "20.5.3-alpha.2",
-    "@angular-eslint/eslint-plugin": "20.5.3-alpha.2",
-    "@angular-eslint/template-parser": "20.5.3-alpha.2"
+    "@angular-eslint/builder": "20.5.3-alpha.4",
+    "@angular-eslint/eslint-plugin": "20.5.3-alpha.4",
+    "@angular-eslint/eslint-plugin-template": "20.5.3-alpha.4",
+    "@angular-eslint/schematics": "20.5.3-alpha.4",
+    "@angular-eslint/template-parser": "20.5.3-alpha.4"
   },
   "ng-update": {
     "packageGroupName": "angular-eslint",