feat: bundle-stats plugin poc implementation · code-pushup/cli@19054d5

TS2769: No overload matches this call. Overload 1 of 2, '(params?: string | { error?: string | $ZodErrorMap<$ZodIssueInvalidType<unknown>> | undefined; message?: string | undefined; } | undefined): ZodString', gave the following error. Object literal may only specify known properties, and 'description' does not exist in type '{ error?: string | $ZodErrorMap<$ZodIssueInvalidType<unknown>> | undefined; message?: string | undefined; }'. Overload 2 of 2, '(params?: string | { error?: string | $ZodErrorMap<$ZodIssueInvalidType<unknown>> | undefined; message?: string | undefined; } | undefined): $ZodType<...>', gave the following error. Object literal may only specify known properties, and 'description' does not exist in type '{ error?: string | $ZodErrorMap<$ZodIssueInvalidType<unknown>> | undefined; message?: string | undefined; }'.

<✓> TypeScript | Semantic errors: packages/models/src/lib/configuration.ts#L4

TS2769: No overload matches this call. Overload 1 of 2, '(params?: string | { error?: string | $ZodErrorMap<$ZodIssueInvalidType<unknown>> | undefined; message?: string | undefined; } | undefined): ZodString', gave the following error. Object literal may only specify known properties, and 'description' does not exist in type '{ error?: string | $ZodErrorMap<$ZodIssueInvalidType<unknown>> | undefined; message?: string | undefined; }'. Overload 2 of 2, '(params?: string | { error?: string | $ZodErrorMap<$ZodIssueInvalidType<unknown>> | undefined; message?: string | undefined; } | undefined): $ZodType<...>', gave the following error. Object literal may only specify known properties, and 'description' does not exist in type '{ error?: string | $ZodErrorMap<$ZodIssueInvalidType<unknown>> | undefined; message?: string | undefined; }'.

<✓> ESLint | Enforce type definitions to consistently use either `interface` or `type`: packages/plugin-bundle-stats/src/lib/runner/audits/details/tree.ts#L36

Use a `type` instead of an `interface`.

<✓> ESLint | Enforce type definitions to consistently use either `interface` or `type`: packages/plugin-bundle-stats/src/lib/runner/audits/details/table.ts#L26

Use a `type` instead of an `interface`.

<✓> ESLint | Enforce type definitions to consistently use either `interface` or `type`: packages/plugin-bundle-stats/src/lib/runner/audits/details/grouping.ts#L59

Use a `type` instead of an `interface`.

<✓> ESLint | Enforce type definitions to consistently use either `interface` or `type`: packages/plugin-bundle-stats/src/lib/runner/audits/details/grouping.ts#L42

Use a `type` instead of an `interface`.

<✓> ESLint | Enforce type definitions to consistently use either `interface` or `type`: packages/plugin-bundle-stats/src/lib/runner/audits/details/grouping.ts#L32

Use a `type` instead of an `interface`.

<✓> ESLint | Return of boolean expressions should not be wrapped into an "if-then-else" statement: packages/plugin-bundle-stats/src/lib/runner/audits/selection.ts#L146

Replace this if-then-else flow by a single return statement.