Matěj Chalk

I was looking into this issue for a little while and had some concerns with the proposed API changes to `select`: 1. It looks like the key-comparison map would be...

> @matejchalk i actually like that idea pretty much. would you like to PR this? Yeah, sure :slightly_smiling_face:

> (Maybe?) Only take the offsetY and offsetX from the HTML Element API instead of just searching for every occurence in the AST Yes, this would be the most robust...

> It looks like there is a problem with the e2e tests setup: > > * `cli-e2e` and `nx-plugin-e2e` declares the same `globalSetup` which is the relative path to `global-setup.e2e.ts`....

@getlarge We've just fixed the [CI](https://github.com/code-pushup/cli/actions/workflows/ci.yml?query=branch%3Amain) and [Code PushUp](https://github.com/code-pushup/cli/actions/workflows/code-pushup.yml?query=branch%3Amain) workflows in `main`. So if you merge `main` into this branch, the workflows should pass and then we can merge this...

Implemented as custom plugin for customer, along JS Packages plugin equivalent for Poetry package manager. code-pushup.pylint.plugin.ts ```typescript import type { Audit, AuditOutput, Group, Issue, IssueSeverity, PluginConfig, } from "@code-pushup/models"; import...

@vmasek I'd suggest closing this research issue in favour of creating new issues to build the official Python plugins based on this prototype.

Could this possibly be related to #529? I plan to fix that by having the ESLint plugin use a temporary file instead of command-line args.

> Is there a way to limit how many Node.js processes that are executed in parallel? We actually don't do any parallel execution at the moment, all plugins are run...

@LayZeeDK Thanks for explaining your use case. I think the memory error could be resolved if we lint projects separately instead of all at once - added more info in...